--- title: "Close CRM Integration" description: "Connect AI agents to Close CRM. Agents manage leads, contacts, opportunities, activities (calls, emails, SMS, meetings), tasks, sequences, bulk actions, and webhooks via OAuth2." url: https://flowrunner.ai/integrations/closecrm date_modified: 2026-08-01T02:40:32-07:00 --- # Close CRM [CRM](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Close CRM. Agents manage leads, contacts, opportunities, activities (calls, emails, SMS, meetings), tasks, sequences, bulk actions, and webhooks via OAuth2. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 20 triggers · 63 actions · OAuth · available [Close CRM website](https://close.com/) · [Platform Documentation](https://developer.close.com/) · Capability data verified 2026-08-12 1. An On Lead Status Changed event fires for a deal moving to qualified 2. Agent reads the lead, the new status, and the most recent activity 3. Agent checks for an existing opportunity and the assigned rep 4. Agent creates an opportunity, subscribes the contact to the qualified-lead sequence, and logs a follow-up task 5. Assigned rep notified with the lead context and the recommended next step 6. Reassignment or sequence-stop decisions routed to the sales lead ## What This Integration Enables Agents read and write across the full Close object model: leads, contacts, opportunities, notes, calls, emails, SMS, meetings, and tasks. They run advanced searches and smart views to segment records before acting, manage sequences with subscribe, pause, and resume actions, and run bulk operations across large lead sets. Twenty triggers cover lead, opportunity, contact, task, note, call, email, SMS, meeting, and custom activity events, so flows react to the moments that move a deal rather than running on a schedule. Configuration reads (pipelines, lead statuses, opportunity statuses, custom fields) let agents validate before they write. The audit log gives a flow a way to inspect what actually happened. ### Without FlowRunner **Manual lead status updates**: Reps update lead status only when they remember, and downstream actions miss the signal **Sequence enrollment by hand**: Contacts are added to sequences one at a time after a rep notices a status change **Activity buried in the timeline**: Calls, emails, and SMS sit in the lead timeline with no automation reading them ### With FlowRunner **Status changes drive workflow**: Every On Lead Status Changed event fires the right downstream action automatically **Sequences and tasks created on signal**: Sequence subscription and follow-up tasks land the moment a lead qualifies **Activity is acted on**: Calls completed, emails received, and SMS exchanges drive context-aware next steps ## Use Case Scenarios ### Qualified Lead to Sequence and Task A lead moves from "New" to "Qualified" in Close and On Lead Status Changed fires. The agent reads the lead, confirms there is no open opportunity, creates one in the right pipeline, subscribes the primary contact to the qualified-lead sequence with Subscribe Contact to Sequence, and creates a follow-up task assigned to the lead's rep. The status change becomes a workflow trigger instead of a note in the timeline. ### Inbound Reply Triage On Email Received fires for a reply on an outbound sequence. The agent pulls the email body and the lead, runs a smart view to check whether the lead is in an active opportunity, and routes the reply: if the lead is in late-stage, Pause Sequence Subscription stops the automation and a Slack notification asks the rep to take the conversation manually; if the lead is early-stage, the agent logs the reply and lets the sequence continue. Sequences stop firing into live conversations. ### Bulk Enrichment Import A list of qualified prospects is exported from a tracker. The agent reads each row, calls Find Lead by Email to check for an existing record, then calls Create Lead or Update Lead with the enriched data and Add Tags to mark the source. After the batch, it posts a summary to the sales channel: how many created, how many updated, how many flagged for review. The import is recorded and re-runnable. ## Human-in-Loop Highlight Bulk operations on a CRM are exactly where an agent should stop and ask before acting. When a Bulk Edit Leads or Bulk Delete Leads run is about to touch a large number of records, the agent stages the change, runs a dry-count, and routes the request to the sales lead via Slack: "Bulk update will modify \[N\] leads matching \[filter\] with \[change\]. Approve, modify the filter, or cancel?" The lead decides. On approval, the agent calls the bulk action and records the result with Get Bulk Action Status. Routine, single-record updates flow through; anything that touches a chunk of the pipeline gets a human in the loop. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via Slack Human decides Agent resumes with decision ## Agent Capabilities 63 actions ### Leads 8 - **List Leads** Lists leads with filtering. Used to feed bulk enrichment and reporting flows. - **Get Lead** Retrieves a single lead. Used to pull full detail for downstream actions. - **Create Lead** Creates a new lead record in Close. Used when importing prospects or capturing inbound leads. - **Update Lead** Updates a lead record. Used to keep status, owner, and custom fields current as work progresses. - **Delete Lead** Removes a lead. Used in data hygiene flows under guard. - **Merge Leads** Merges two lead records. Used in duplicate-resolution flows under approval. - **Find Lead by Email** Searches and retrieves a lead by email. Used as the first step in inbound-lead routing to avoid duplicates. - **Find Lead by Phone** Searches and retrieves a lead by phone number. Used in call-driven workflows. ### Contacts 5 - **List Contacts** Lists contacts at a lead. Used to enumerate the stakeholder map. - **Get Contact** Retrieves a contact. Used to pull contact detail for routing or messaging. - **Create Contact** Creates a contact on a lead. Used to add a new stakeholder as the deal develops. - **Update Contact** Updates a contact's details. Used to keep title, phone, or email current. - **Delete Contact** Removes a contact. Used in cleanup flows. ### Opportunities 5 - **List Opportunities** Lists opportunities. Used in pipeline reporting and bulk processing. - **Get Opportunity** Retrieves a single opportunity. Used for context before taking action. - **Create Opportunity** Creates an opportunity on a lead. Used to open a deal when a lead qualifies. - **Update Opportunity** Updates an opportunity. Used to move stage, value, or close date. - **Delete Opportunity** Deletes an opportunity. Used to clean up records under guard. ### Activities (Notes, Calls, Emails, SMS, Meetings) 16 - **List Notes** Lists notes on a lead. Used to pull conversation history into a flow. - **Create Note** Adds a note to a lead. Used to log workflow-driven context. - **Update Note** Edits an existing note. Used to extend or correct logged context. - **Delete Note** Removes a note. Used in cleanup flows. - **List Calls** Lists call records. Used in call-outcome reporting. - **Log Call** Logs a manual or external call against a lead. Used to record activity from outside Close. - **Update Call** Updates a call record. Used to correct outcome or duration after the fact. - **Delete Call** Removes a call record. Used in cleanup flows. - **List Emails** Lists email activity on a lead. Used to pull communication history. - **Send Email** Sends an email through Close. Used to deliver a workflow-driven message in the lead's thread. - **Delete Email** Removes an email record. Used in cleanup flows. - **List SMS** Lists SMS activity. Used to pull the SMS history into a flow. - **Send SMS** Sends an SMS through Close. Used to deliver a workflow-driven text in the lead's thread. - **Delete SMS** Removes an SMS record. Used in cleanup flows. - **List Meetings** Lists meeting records. Used in calendar-based workflows. - **Get Meeting** Retrieves a meeting record. Used to pull meeting detail for follow-up actions. ### Tasks 5 - **List Tasks** Lists open and completed tasks. Used in workload and follow-up reporting. - **Create Task** Creates a task on a lead. Used to set a workflow-driven follow-up for a rep. - **Update Task** Updates a task. Used to change due date, owner, or status. - **Complete Task** Marks a task complete. Used when the workflow finishes the work behind it. - **Delete Task** Removes a task. Used in cleanup flows. ### Search and Configuration 10 - **List Activities** Lists the unified activity feed. Used to drive flows that read the timeline. - **List Pipelines** Lists opportunity pipelines. Used to route deals to the right pipeline. - **List Lead Statuses** Lists configured lead statuses. Used to validate before writing. - **List Opportunity Statuses** Lists configured opportunity statuses. Used to validate stage moves. - **List Custom Fields** Lists configured custom fields. Used to map workflow data to the right slot. - **List Custom Object Types** Lists configured custom object types. Used in advanced custom-data flows. - **Get Me** Retrieves the authenticated Close user. Used to confirm the connected account. - **List Users** Lists Close users. Used to route assignments and approvals. - **Run Advanced Search** Runs a Close advanced search. Used to segment leads or opportunities before acting. - **Run Smart View** Runs a saved Smart View. Used to drive flows from team-curated segments. ### Sequences 4 - **List Sequences** Lists email sequences. Used to choose the right sequence in a flow. - **Subscribe Contact to Sequence** Subscribes a contact to a sequence. Used to enroll qualified leads automatically. - **Pause Sequence Subscription** Pauses a contact's sequence. Used when a reply lands and the sequence should stop. - **Resume Sequence Subscription** Resumes a paused sequence. Used when a hold is lifted. ### Bulk Actions and Webhooks 8 - **Bulk Edit Leads** Bulk-edits a set of leads. Used in approved, large-scale updates. - **Bulk Delete Leads** Bulk-deletes a set of leads. Used in approved cleanup flows. - **Bulk Email** Sends a bulk email to a set of contacts. Used in approved outreach flows. - **Get Bulk Action Status** Retrieves the status of a running bulk action. Used to confirm completion. - **List Webhooks** Lists configured webhooks. Used in trigger-management flows. - **Create Webhook** Creates a webhook subscription. Used to register a new trigger source. - **Update Webhook** Updates a webhook subscription. Used to adjust an existing trigger. - **Delete Webhook** Removes a webhook subscription. Used in cleanup flows. ### Audit and Files 2 - **List Events** Lists Close audit log events. Used to inspect what happened during a workflow. - **Upload File** Uploads a file against a Close record. Used to attach contracts or supporting documents. ## Triggers 20 triggers ### Event Triggers 20 - **On Lead Created** Fires when a new lead is created in Close. Initiates intake and routing flows. - **On Lead Updated** Fires when a lead record is updated. Initiates flows that react to field changes. - **On Lead Status Changed** Fires when a lead moves between statuses. Initiates qualification and pipeline-progression flows. - **On Lead Deleted** Fires when a lead is deleted. Initiates cleanup and downstream-sync flows. - **On Lead Merged** Fires when two leads are merged. Initiates flows that reconcile downstream references. - **On Opportunity Created** Fires when a new opportunity is opened. Initiates sales-alerting and tracker flows. - **On Opportunity Updated** Fires when an opportunity is updated. Initiates flows that react to stage or value changes. - **On Opportunity Status Changed** Fires when an opportunity moves status. Initiates win, loss, and progression flows. - **On Contact Created** Fires when a new contact is added to a lead. Initiates stakeholder-tracking flows. - **On Contact Updated** Fires when a contact is updated. Initiates enrichment and sync flows. - **On Task Created** Fires when a new task is created. Initiates workload-routing flows. - **On Task Completed** Fires when a task is marked complete. Initiates downstream follow-up flows. - **On Note Created** Fires when a note is added to a lead. Initiates flows that read written context. - **On Call Completed** Fires when a call is logged as completed. Initiates call-outcome flows. - **On Email Sent** Fires when an outbound email is sent. Initiates tracking and reporting flows. - **On Email Received** Fires when an inbound email is received. Initiates reply-triage flows. - **On SMS Sent** Fires when an outbound SMS is sent. Initiates SMS reporting flows. - **On SMS Received** Fires when an inbound SMS is received. Initiates SMS-triage flows. - **On Meeting Completed** Fires when a meeting is marked complete. Initiates post-meeting follow-up flows. - **On Custom Activity Created** Fires when a custom activity is created. Initiates flows that react to organization-specific events. ## Frequently Asked Questions ### What can FlowRunner do with Close CRM? FlowRunner agents can run List Leads, Get Lead, and Create Lead in Close CRM, plus 60 more actions. ### Does connecting Close CRM to FlowRunner require OAuth? Yes. Close CRM connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials. ### Can Close CRM trigger a FlowRunner workflow automatically? Yes. Close CRM supports 20 triggers that can start a FlowRunner workflow automatically. **Work at Close CRM?** This integration exposes Close CRM to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/closecrm. Site index: https://flowrunner.ai/llms.txt