Capsule CRM MCP integration for AI agents.
Connect AI agents to Capsule CRM through 25 structured actions, including get current user, create opportunity, and delete opportunity. Review authentication…
- ACTION CONTRACTS
- 25
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Capsule CRM integration exposes
The Capsule CRM Agent App exposes 25 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent read the capsule crm user associated with the access token, create a capsule crm opportunity, and delete a capsule crm opportunity. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Capsule CRM account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Capsule CRM capabilities.
Showing 12 of 25 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_current_userREADRead the Capsule CRM user associated with the access token.
INPUTS: embed
create_opportunityWRITECreate a Capsule CRM opportunity.
INPUTS: opportunity
delete_opportunityHIGH IMPACTDelete a Capsule CRM opportunity.
INPUTS: id
create_partyWRITECreate a Capsule CRM party.
INPUTS: party
create_taskWRITECreate a Capsule CRM task.
INPUTS: task
delete_partyHIGH IMPACTDelete a Capsule CRM party.
INPUTS: id
delete_taskHIGH IMPACTDelete a Capsule CRM task.
INPUTS: id
get_opportunityREADRead one Capsule CRM opportunity by ID.
INPUTS: id
get_partyREADRead one Capsule CRM party by ID.
INPUTS: id
get_taskREADRead one Capsule CRM task by ID.
INPUTS: id
list_categoriesREADList Capsule CRM task categories.
INPUTS: page / perPage
list_countriesREADList countries supported by Capsule CRM.
INPUT CONTRACTS
Know what the action needs before it runs.
get_current_user
embedOPTIONAL- Additional related resources to embed in the Capsule CRM response.
create_opportunity
opportunityOPTIONAL- The Capsule CRM opportunity payload to send.
delete_opportunity
idOPTIONAL- The unique Capsule CRM opportunity ID.
create_party
partyOPTIONAL- The Capsule CRM party payload to send.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Current User
Read the Capsule CRM user associated with the access token. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_current_userControl Create Opportunity
Create a Capsule CRM opportunity. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_opportunityVerify with Get Opportunity
Read one Capsule CRM opportunity by ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_opportunitySAFETY BOUNDARY
Operate Capsule CRM with explicit limits
- Authorize Capsule CRM with API key and grant only the provider access required by the selected actions.
- 9 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_opportunity`, `delete_party`, and `delete_task` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Capsule CRM rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Capsule CRM task completed successfully.
CONNECTION MODEL
API key
Capsule CRM personal access token sent as Authorization: Bearer <token>. Create one from Capsule account settings.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 16
- WRITE SIGNALS
- 6
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Capsule CRM.