Composio is a bridge that exposes pre-built actions across 250+ SaaS apps (Slack, Gmail, Google Sheets, HubSpot, Salesforce, Notion and more) to the agent through the Model Context Protocol, so it can act in those apps alongside your ad accounts.

How do I connect Composio to Agent Planners?

Get an API key from app.composio.dev (Settings → API Keys), paste it into the Composio card on the Integrations page, then connect the specific apps you want with the per-app Connect buttons. Connected actions appear to the agent automatically.

Why can't the agent use my Composio app?

An API key alone only loads the catalog — you must connect the app from the card so the connection is made under your workspace; a connection created only in the Composio dashboard won't be usable. Also mention the app in your goal so the planner surfaces its actions.

Are Composio actions safe?

Yes — your key is encrypted and scoped to your org, and every external write pauses at the same approval gate as ad-account writes. Reads run as part of the plan; nothing is sent or changed without your approval.

Composio vs a custom MCP server — which do I use?

Use Composio for pre-built SaaS actions you don't want to build. Use a custom MCP server to expose your own internal tools or data over an endpoint you host. See the MCP guide for the custom path.

Extend

Connect & use Composio

TL;DR

Composio is a bridge that exposes pre-built actions across 250+ SaaS apps to the agent through the Model Context Protocol. Add your Composio API key on the Integrations page, connect the specific apps you want, and the agent can read from and act in them — send a Slack message, email a report, create a Linear issue, sync to a Google Sheet — alongside your ad accounts. Every write still pauses for your approval.

What Composio adds

On its own, Agent Planners runs across your ad stack — Google Ads, GA4, BigQuery and Search Console. Composio extends that reach: one API key unlocks pre-built actions for 250+ other SaaS apps (Slack, Gmail, Google Sheets/Calendar, Notion, HubSpot, Salesforce, Linear, Jira, GitHub and more), so the agent can wire your ad ops into the rest of your stack.

The actions are surfaced to the agent the same way as a custom MCP server — the planner sees the connected tools and calls them by name when a goal needs them.

Get your Composio API key

1Sign in (or sign up) at app.composio.dev.
2Go to Settings → API Keys.
3Create or copy a key — it starts with “ak_”.

The key is stored encrypted with your organization's secret and is never returned to the browser or in API responses.

Connect Composio in Agent Planners

Open the Integrations page and find the Composio (MCP) card.

1Paste your Composio API key into the card and click Save — the key is verified, then encrypted.
2Connect the specific apps you want: use the per-app Connect buttons on the card to authorize each toolkit (e.g. Slack, Gmail) for this workspace.
3Once an app is connected, its actions appear to the agent automatically — no extra wiring.

Important: a key alone only loads the catalog. The agent can only EXECUTE an app's actions after you connect that app from the card, because the connection must be made under this workspace — a connection created only in the Composio dashboard won't be usable here.

How the agent uses Composio actions

When your goal involves a connected app, the planner includes its actions in the plan and calls them mid-run, exactly like built-in tools. Results flow back into the run and the final report.

Reads (fetch a message, list records) run as part of the plan.
Writes (send a message, create / update / delete a record) always pause at the approval gate — in-app or by email — before they ship.
Connected actions are surfaced to the planner when your goal references the app or a cross-app task, so pure ad-ops goals stay fast.

Example things you can ask

“Email me the weekly performance review every Monday.” (Gmail)
“Post a summary of today's optimizations to our #ads Slack channel.” (Slack)
“Create a Linear issue for every disapproved ad with its policy topic.” (Linear)
“Append this week's flagged campaigns to my Google Sheet.” (Google Sheets)
“Log the budget changes I approved to our HubSpot deal.” (HubSpot)

Security & approvals

Your Composio key is encrypted at rest and scoped to your organization.
Every external write goes through the same approval gate as ad-account writes — nothing is sent or changed without your go-ahead.
Connections are scoped to your workspace; remove the key any time to revoke access.

Troubleshooting

Symptom	Fix
“Key rejected by Composio”	The key is invalid or expired — paste a fresh one from app.composio.dev → Settings → API Keys.
“Reachable but no tools returned”	You added a key but haven't connected any app — connect one from the card, then refresh.
Agent doesn't use a connected app	Mention the app or the cross-app task in your goal so the planner surfaces its actions.

Frequently asked questions

What is Composio?: Composio is a bridge that exposes pre-built actions across 250+ SaaS apps (Slack, Gmail, Google Sheets, HubSpot, Salesforce, Notion and more) to the agent through the Model Context Protocol, so it can act in those apps alongside your ad accounts.
How do I connect Composio to Agent Planners?: Get an API key from app.composio.dev (Settings → API Keys), paste it into the Composio card on the Integrations page, then connect the specific apps you want with the per-app Connect buttons. Connected actions appear to the agent automatically.
Why can't the agent use my Composio app?: An API key alone only loads the catalog — you must connect the app from the card so the connection is made under your workspace; a connection created only in the Composio dashboard won't be usable. Also mention the app in your goal so the planner surfaces its actions.
Are Composio actions safe?: Yes — your key is encrypted and scoped to your org, and every external write pauses at the same approval gate as ad-account writes. Reads run as part of the plan; nothing is sent or changed without your approval.
Composio vs a custom MCP server — which do I use?: Use Composio for pre-built SaaS actions you don't want to build. Use a custom MCP server to expose your own internal tools or data over an endpoint you host. See the MCP guide for the custom path.