Bulk Delete Completed
Triggers when a bulk delete finishes.
Close is a CRM platform designed to help businesses manage and streamline their sales processes, including calling, email automation, and predictive dialers.
Triggers when a bulk delete finishes.
Triggers when a bulk delete is started.
Triggers when a bulk delete makes progress, carrying how many records it has handled so far.
Triggers when a bulk edit finishes.
Triggers when a bulk edit is started.
Triggers when a bulk edit makes progress, carrying how many records it has handled so far.
Triggers when a bulk email send is started.
Triggers when a bulk email send is paused, either by a person or by Close itself.
Triggers when a bulk email send makes progress, carrying how many recipients it has handled so far.
Triggers when a bulk sequence action finishes.
Triggers when a bulk sequence subscribe, pause or resume is started.
Triggers when a bulk sequence action makes progress, carrying how many contacts it has handled so far.
Triggers when a call is deleted from a lead's timeline.
Triggers when a call is recorded on a lead, whether placed through Close or logged after the fact. Filter on `direction` for inbound only.
Triggers when a recorded call changes, such as its note, outcome, recording or transcript.
Triggers when a comment is posted on an activity or object. The first comment on an object also opens a thread, which fires CLOSE_COMMENT_THREAD_STARTED in the same request.
Triggers when a custom activity instance is deleted from a lead.
Triggers when an instance of a custom activity type is logged on a lead. Filter on `custom_activity_type_id` for one type only.
Triggers when an existing custom activity instance changes.
Triggers when an email is deleted from a lead's timeline.
Triggers when an email is recorded on a lead, whether it arrived, was drafted, was scheduled, or was logged as already sent. Filter on `direction` for inbound only.
Triggers when an email thread is deleted from a lead.
Triggers when a new email thread appears on a lead. The individual messages arrive separately on CLOSE_EMAIL_LOGGED.
Triggers when an email thread changes, such as a message being added to it or its subject changing.
Triggers when a recorded email changes, such as a draft being edited, an open being recorded, or its status moving.
Triggers when the 'Lead Created' entry is added to a lead's timeline. This fires alongside CLOSE_LEAD_CREATED for the same lead and adds the timeline position and the import that produced it.
Triggers when a 'Lead Created' timeline entry is removed, which means its lead was deleted.
Triggers when a 'Lead Created' timeline entry is moved to a different lead, which in practice means its lead was merged into another.
Triggers when a lead-status-change entry is removed from a lead's timeline.
Triggers when Close folds a further status change into an existing lead- status-change timeline entry, which happens when the lead changes status twice in quick succession.
Triggers when a lead moves to a different lead status, carrying both the old and the new status. This is the status-change event itself; CLOSE_LEAD_UPDATED also fires for the same move.
Triggers when a note is written on a lead.
Triggers when a note is deleted from a lead.
Triggers when an existing note is edited.
Triggers when an opportunity-status-change entry is removed from a lead's timeline.
Triggers when Close folds a further status change into an existing opportunity-status-change timeline entry.
Triggers when an opportunity moves to a different status, carrying the old and new status, its type (`active`, `won` or `lost`) and the pipeline. Filter on `new_status_type` for a deal-won automation.
Triggers when an SMS is deleted from a lead's timeline.
Triggers when an SMS is recorded on a lead. Filter on `direction` for inbound only.
Triggers when a recorded SMS changes, such as its status moving or a delivery error being recorded.
Triggers when a 'task completed' entry is removed from a lead's timeline.
Triggers when a 'task completed' entry appears on a lead's timeline. The task itself also fires its own completion trigger, such as CLOSE_LEAD_TASK_COMPLETED.
Triggers when a WhatsApp message is deleted from a lead's timeline.
Triggers when a WhatsApp message is recorded on a lead. Its `direction` is `incoming` or `outgoing`, not the `inbound`/`outbound` the other communication triggers use.
Triggers when a recorded WhatsApp message changes.
Creates a new call record in Close.com. This tool allows you to log both inbound and outbound calls associated with a lead, supporting parameters such as lead_id, direction, and optional support for contact_id, phone, duration, note, recording_url, and user_id.
Create or log a Close email activity. Draft creates an unsent activity. Scheduled and outbox are send-capable modes that can deliver email externally; inbox, sent, and error log outcomes. Setting followup_date can also create a follow-up task if no reply is received.
Creates a new lead in Close CRM. A lead represents a company or organization in your sales pipeline. This tool allows you to create leads with company information (name, description, website), associate contacts with emails/phones/URLs, add addresses, and set the lead status. Contacts and addresses can be nested in the lead creation request. The tool returns comprehensive lead information including the lead ID, direct URL to view in Close CRM, associated contacts with their IDs, addresses, status information, and creation/update timestamps. Note: Activities, tasks, and opportunities must be created separately after lead creation.
This tool creates a new SMS activity in Close CRM. It is primarily used to log SMS communications, including sent messages, received messages, and draft messages. The tool requires an internal phone number (local_phone) which must be an SMS-enabled phone number owned by your Close organization. Note: Actually sending SMS messages (status 'outbox' or 'scheduled') requires A2P 10DLC compliance.
This tool creates a new task in Close.com. Tasks are used to track to-do items and can be associated with leads. The tool will create a task with the specified parameters using the provided text, due_date, and is_complete flags.
This tool allows you to delete a specific call activity in Close.com. It is useful for removing incorrectly logged calls or cleaning up call records. The action deletes a call activity using its unique call ID and cannot be undone.
Retrieve one Close contact by ID, optionally limiting returned fields.
This tool retrieves a list of note activities from Close. It allows users to fetch notes with optional filtering parameters, including filtering by lead_id, user_id, and date ranges. The tool returns details such as note content, creation and update dates, and any associated attachments.
Retrieve one Close opportunity by ID with optional field projection.
Lists one page of Close email or call activities using documented filters.
This tool lists the custom activity types defined in a Close organization, returning each type's id and name. Use it to find the custom activity type id that filters a custom activity trigger, or before creating a custom activity instance of a given type.
This tool lists the custom object types defined in a Close organization, returning each type's id and name. Use it to find the custom object type id that filters a custom activity trigger, or before creating a custom activity instance of a given type.
List Close opportunities with aggregate values and offset pagination.
Return the identity (email, name) of the connected Close account.
The Close integration connects your Dench AI CRM directly to Close, so agents can read and act on your Close data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
14 actions are available for agents to invoke on your behalf, and 45 triggers can start a Dench automation the moment something changes in Close. Every call runs through Close's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Close and click Connect — you'll authorize access through Close's own sign-in flow. No API keys or code required.
Ask an agent to use Close in chat, or wire a Close trigger into an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Close integration connects your AI CRM to Close, so AI agents can work with your Close data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Close integration currently exposes 14 actions, including Create Call, Create Email, Create Lead, Create SMS Message, Create Task, and Delete Call. Agents invoke them on your behalf from chat or from automations.
Yes. The Close integration provides 45 triggers — such as Bulk Delete Completed, Bulk Delete Created, Bulk Delete Updated, and Bulk Edit Completed — that can start a Dench automation the moment something happens in Close.
No. You connect Close from your Dench workspace using Close's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Close's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Close connection from your workspace settings at any time.