Verified Agent Skill record

Capsule CRM Automation

Capsule CRM Automation uses the Composio MCP integration to manage contacts, query parties, opportunities, and projects, track tasks, browse activity entries, list organization employees, and list deleted opportunities through natural-language requests.

Tasks

Run structured filter queries across parties, opportunities, and projects, which the API identifies as `kases`.
List, create, update, and delete Capsule CRM contacts.
List tasks and projects, and browse activity entries.
List employees associated with an organization.
List deleted opportunities modified since a specified date.

Inputs

Natural-language requests describing the desired Capsule CRM operation.
Filter entities, conditions, operators, values, sorting, embedding, and pagination settings for structured queries.
Contact details such as names, email addresses, phone numbers, addresses, organizations, tags, custom fields, websites, and owner IDs.
A party ID and party update object when updating a contact.
A party ID when deleting a contact.
An organization ID when listing organization employees.
An ISO8601 `since` value when listing deleted opportunities.
Optional status, search, modification-date, embedding, and pagination filters for supported list operations.

Outputs

Filtered parties, opportunities, or projects.
Contact listings with requested embedded related data.
Created or updated contact records.
The result of a requested contact deletion.
Task, project, and activity-entry listings.
Employees associated with a specified organization.
A listing of deleted opportunities since the specified date.

Limitations and checks

Structured filter queries accept only `parties`, `opportunities`, or `kases` as documented entity values.
List operations default to 50 items per page where stated and allow at most 100 items per page.
Country filters require ISO 3166-1 alpha-2 codes.
Removing contact sub-items requires each item's ID together with `_delete: true`.
Embed options vary by entity and endpoint.
For address filters, use top-level fields such as `city`, `state`, `country`, and `zip`; do not use nested forms such as `address.state`.
Use `kases`, not `projects`, as the entity value in structured project filter queries.
Express country values as ISO alpha-2 codes such as `US`, `GB`, or `CA`.