--- title: "Capsule CRM Integration" description: "Connect AI agents to Capsule CRM. Agents sync people and organizations from other systems, create and advance sales opportunities through pipelines, open and close cases, manage tasks, and read pipelines, milestones, tags, and custom fields." url: https://flowrunner.ai/integrations/capsule-crm date_modified: 2026-08-01T02:40:32-07:00 --- # Capsule CRM [CRM](https://flowrunner.ai/integrations/category/crm-sales) Connect AI agents to Capsule CRM. Agents sync people and organizations from other systems, create and advance sales opportunities through pipelines, open and close cases, manage tasks, and read pipelines, milestones, tags, and custom fields. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 31 actions · API key · available [Capsule CRM website](https://capsulecrm.com/) · [Platform Documentation](https://developer.capsulecrm.com/) · Capability data verified 2026-08-12 1. A new order arrives from the storefront 2. Agent pulls the buyer's name, email, and order details 3. Search Parties looks for an existing person matched on email 4. Create Person adds the buyer, or Update Party refreshes the existing record 5. Create Opportunity opens the follow-up deal at the right milestone 6. The sales channel gets a summary with links to the new records 7. The account owner reviews the day's new opportunities and picks priorities ## What This Integration Enables Capsule is the CRM for teams that want pipeline discipline without hiring an admin to enforce it. This connector makes a FlowRunner agent that admin. Agents sync people and organisations in from the storefront and the inbox, open and advance opportunities through your pipelines, run cases for onboarding and client work, and manage the follow-up tasks that keep deals moving. They read your pipelines, milestones, tags, and custom fields at runtime, so workflows fit the Capsule you configured rather than a generic one. One class of operation stays with people. Deletion in Capsule is permanent, and the [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate on it matters most where deletion is also a legal act: honoring a right-to-erasure request correctly, completely, and on purpose. ### Without FlowRunner **Pipeline discipline as headcount**: Keeping Capsule current is a part-time job nobody was hired for **Customers invisible to sales**: Buyers exist in the storefront and inbox but never make it into the CRM **Erasure requests handled nervously**: Right-to-be-forgotten deletions happen ad hoc, with no record of what was checked first ### With FlowRunner **An agent as the CRM admin**: Contacts, opportunities, and cases stay current without anyone retyping **Every buyer in the pipeline**: Orders and signups become people and opportunities on arrival **Erasure with evidence and sign-off**: Deletion requests arrive verified, with attached context reviewed by a person first ## Use Case Scenarios ### From checkout to pipeline before the confirmation email lands An order from [Shopify](https://flowrunner.ai/integrations/shopify) reaches the agent. Search Parties checks for the buyer by email. New buyers get a Create Person with the details mapped to your custom fields; returning ones get an Update Party refresh. Create Opportunity opens the follow-up deal on the right pipeline at the right milestone, resolved at runtime from List Pipelines and List Milestones, and Create Task schedules the first touch. The sales team's morning starts with a pipeline that already reflects yesterday's buyers. ### Onboarding as a case, not a memory When a deal closes, the agent opens a Create Case against the client's party, emails the kickoff details through [Gmail](https://flowrunner.ai/integrations/gmail-service), and creates the onboarding task sequence with owners and due dates. As tasks complete, Update Case keeps the record current, and when the last step clears, the case closes. Each evening, List Opportunities feeds the day's movement into [Google Sheets](https://flowrunner.ai/integrations/google-sheets) and a pipeline summary posts to [Slack](https://flowrunner.ai/integrations/slack). Client work stops living in whoever ran the last onboarding. ### Right-to-erasure requests, verified and signed off An erasure request comes in. The agent verifies the requester's identity against the record, then assembles what deletion actually touches: the party via Get Party, open deals from List Opportunities, active cases from List Cases, and pending tasks. That dossier goes to the data owner, because Delete Party is permanent and takes the relationship's history with it. On approval, the agent deletes, confirms completion, and logs when the request was honored. Compliance work that used to be nervous guesswork becomes a repeatable process with a paper trail. ## Human-in-Loop Highlight Delete Party permanently removes a person or organisation from Capsule, along with the context attached to them, and in an erasure workflow it is pointed at a record that may still have an open opportunity or an active case. So the agent never deletes on receipt. It posts to the data owner: "Erasure request verified for J. Meyer. The party has one open opportunity at Proposal worth review before deletion, and one active onboarding case. Deleting is permanent. Approve deletion, or resolve the open items first?" The owner decides the order of operations. The request gets honored fully, and nothing a live deal depended on vanishes as a side effect. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 31 actions ### Parties 7 - **List Parties** Lists people and organisations, most recently updated first. Used for sync sweeps and audits. - **Get Party** Retrieves a single party by ID. Used to gather full context before updates or deletion decisions. - **Search Parties** Searches parties by free text across names, emails, and phone numbers. The dedup check before any create. - **Create Person** Creates a person party. The capture step for new buyers and signups. - **Create Organisation** Creates an organisation party. Used when a new company enters the pipeline. - **Update Party** Updates a person or organisation. Used for enrichment and refresh passes. - **Delete Party** Permanently deletes a party. The operation this page's human gate exists for. ### Opportunities 6 - **List Opportunities** Lists opportunities, most recently updated first. The backbone of pipeline reports. - **Get Opportunity** Retrieves a single opportunity by ID. - **Search Opportunities** Searches opportunities by free text across name, description, and related party. - **Create Opportunity** Creates a sales opportunity. The step that turns a buyer into pipeline. - **Update Opportunity** Updates an opportunity. The milestone-advancement step as deals progress. - **Delete Opportunity** Permanently deletes an opportunity. Used only in reviewed cleanup. ### Cases 5 - **List Cases** Lists cases, most recently updated first. Used to track open client work. - **Get Case** Retrieves a single case by ID. - **Create Case** Creates a case linked to a party. The step that turns a closed deal into a structured onboarding. - **Update Case** Updates a case. Used to progress and close client work as tasks complete. - **Delete Case** Permanently deletes a case. Used only in reviewed cleanup. ### Tasks 5 - **List Tasks** Lists tasks filtered by open, completed, or pending status. Used to find overdue follow-ups. - **Get Task** Retrieves a single task by ID. - **Create Task** Creates a task. The step that turns workflow findings into assigned follow-ups. - **Update Task** Updates a task. Used to reassign owners as deals progress. - **Delete Task** Permanently deletes a task. ### Configuration and Reference 8 - **List Projects** Lists the Kanban-style project boards configured in Capsule. - **List Users** Lists account users with name and status. Used to resolve assignees at runtime. - **List Teams** Lists the teams configured in the account. - **List Tags** Lists tags for a record type. Used so workflows apply your taxonomy, not an invented one. - **List Custom Fields** Lists custom field definitions for a record type. Used to map incoming data to the fields your team reports on. - **List Pipelines** Lists the sales pipelines configured in the account. - **List Milestones** Lists pipeline milestones. Used to place new opportunities at the correct stage. - **List Categories** Lists task categories. Used to file follow-ups where your team expects them. ## Frequently Asked Questions ### What can FlowRunner do with Capsule CRM? FlowRunner agents can run List Parties, Get Party, and Search Parties in Capsule CRM, plus 28 more actions. ### Does connecting Capsule CRM to FlowRunner require OAuth? No. Capsule CRM connects to FlowRunner with an API key, no OAuth flow required. ### Can Capsule CRM trigger a FlowRunner workflow automatically? Capsule CRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at Capsule CRM?** This integration exposes Capsule 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/capsule-crm. Site index: https://flowrunner.ai/llms.txt