How to connect Composio to Agent Planners
Composio gives an AI agent one-key access to 250+ pre-built SaaS actions — Slack, Gmail, HubSpot, Notion and more — without building each integration yourself. Connecting it to Agent Planners takes one field: paste your Composio API key on the Integrations page, and every agent in your organization can use whatever apps you've connected in your Composio dashboard. Here's the exact flow, including the one gotcha that trips people up.
Step 1: Get your Composio API key
- 1Sign in at composio.dev and go to Settings → API Keys.
- 2Copy your key — it starts with the prefix ak_.
- 3Keep the tab open; you'll want it again if you ever need to rotate the key.
Step 2: Paste it into Agent Planners
- 1Open the Integrations page in your organization.
- 2Paste the key into the Composio API key field and click Save.
- 3Agent Planners test-calls Composio live before confirming — a key Composio rejects (expired or invalid) is reported back to you immediately rather than silently stored as dead.
- 4The key is encrypted at rest, and a success toast confirms it's saved and verified.
Step 3: Connect apps in Composio, then refresh
Connecting apps (Slack, Gmail, HubSpot, whatever you need) happens on Composio's own dashboard, not inside Agent Planners — that's where OAuth for each individual app lives. Once you've connected a new app there, come back to the Integrations page and click Refresh: this re-pulls both your tool catalog and your list of connectable apps without needing a full page reload.
What connecting Composio actually unlocks
Once connected, any agent's plan can call a Composio-backed tool the same way it calls a native platform tool — the orchestrator sees what's available and can route a step to it. This is genuinely different from writing a custom MCP server: Composio is the fast path for common SaaS apps someone else already built the integration for. For when a custom MCP server is the better fit instead — your own internal tools, proprietary data, an app Composio doesn't cover — see Composio vs custom MCP.
Disconnecting
Removing the key disconnects every Composio tool for the organization at once — Agent Planners asks you to confirm before doing it, the same confirmation pattern used before disconnecting an ad account or an MCP server, since it's a one-click action with a wide blast radius.
Frequently asked questions
- Where do I get a Composio API key?
- At app.composio.dev under Settings → API Keys. The key starts with the prefix ak_.
- Does Agent Planners verify the Composio key when I save it?
- Yes — it test-calls Composio live before confirming, so an expired or invalid key is reported back immediately instead of being stored as silently broken.
- I connected a new app in Composio but don't see it in Agent Planners — why?
- Click Refresh on the Integrations page. New apps and tools you connect on Composio's own dashboard need a refresh to re-pull into Agent Planners; it doesn't happen automatically without a page reload otherwise.
- Is my Composio API key stored securely?
- Yes — it's encrypted at rest, the same handling as other connected credentials.
- What happens if I remove my Composio key?
- Every Composio-backed tool becomes unavailable to every agent in the organization immediately. Agent Planners asks for confirmation before this because of how broad the effect is.