Composio

To connect Composio toolkits, open the in-app Connections settings.

Composio is a broker that exposes actions on third-party SaaS apps to Dispatch. Rather than building a one-off connector for every app, Dispatch pulls in actions through Composio's toolkit catalog. After you authorize a toolkit, the corresponding actions become available to the agent.

Dispatch exposes a curated set of Composio toolkits rather than the whole catalog. The toolkits currently available are:

• CRM: Salesforce, HubSpot, Nutshell.
• Files and storage: Google Drive, Dropbox.
• Documents and tasks: Google Docs, Google Sheets, Google Tasks.
• Meetings and video: Zoom, Microsoft Teams, Fireflies.
• Scheduling: Calendly.
• Productivity and project management: Motion, Trello.
• Payments and accounting: Stripe, QuickBooks.
• Social: LinkedIn, Facebook (Pages), Instagram (Business and Creator).
• Messaging and outreach: WhatsApp (Business), Instantly.

This list is maintained by Dispatch and changes as toolkits are added or removed.

How the connection works

Composio is connected once at the account level. From there, you authorize individual toolkits inside Composio's flow; each toolkit corresponds to one third-party app and one set of actions. Authorized toolkits surface to Dispatch as a dynamic set of tools.

Because the toolkit list depends on what you have authorized, the composio connector is registry-presence-only: its tools are materialized at run time during agent setup based on your active toolkits, not declared statically.

Read and write capabilities

These depend entirely on the toolkit. Read-shaped actions (search, fetch, list) and write-shaped actions (create, update, send) both exist for most toolkits.

What automations can use

• Scheduled actions that read or write through Composio toolkits.
• Trigger automations using the same dispatched-from-event model as other automations.

Limits and behavior

• Toolkit availability. Only the curated toolkits listed above are offered, and within those, only the ones you have authorized are active. Authorizing a toolkit makes its actions available to the agent.
• Permission gating. Composio tools are not currently routed through the permission gate. Native connectors (Gmail, Calendar, Slack, etc.) annotate write tools as external-write and pass them through the validator; Composio tools materialized at run time do not carry that annotation. Treat Composio writes with the same care you would the underlying app's API.
• Latency. Composio sits between Dispatch and the third party; tool calls may have higher latency than calls against native connectors.
• No app-specific UX. Dispatch treats Composio toolkits as generic actions. There is no app-specific UI layered on top of any specific Composio toolkit; the user-facing flow is chat plus the standard memory layer.

Related

• Permission gate: how native connector writes are gated.
• Connectors: how the Composio broker fits into the connector model.
• Cookbook: CRM sync: use a connected CRM to enrich people and log activity back.