Connect Composio

Set up the Composio broker that powers every Cyborg7 integration, then connect your first toolkit.

Composio is the broker behind Cyborg7's integrations. It handles the OAuth with each provider (Gmail, Slack, Jira, …) and exposes their actions to a cybo as tools. You connect Composio once; after that, connecting any individual toolkit is a couple of clicks.

Before you start

  • You are a workspace admin (only admins configure the broker and grant toolkits).
  • You have a Composio account at composio.dev.

Step 1 — Get your Composio API key

  1. Sign in at app.composio.dev.
  2. Open Settings → API Keys.
  3. Create a key and copy it (it starts with ck_…). Treat it like a password.

Step 2 — Add the key to Cyborg7

  1. In Cyborg7, open Settings → Integrations → Composio.
  2. Paste the API key and Save.
  3. Cyborg7 validates the key and the broker shows Connected.

Self-hosted deployments can instead set the key as the COMPOSIO_API_KEY environment variable on the daemon/relay; the Settings screen will show it as configured.

Step 3 — Connect a toolkit

  1. Still under Settings → Integrations, pick a toolkit (e.g. Slack).
  2. Choose Personal (your account) or Shared workspace account (admin, for unattended runs).
  3. Complete the provider's OAuth popup and approve the scopes.
  4. The toolkit flips to Connected.

Step 4 — Grant it to a cybo

  1. Open the cybo's Settings → Tools.
  2. Enable the toolkit and, optionally, restrict it to specific actions.
  3. Set an approval policy (auto-run vs ask-first) for sensitive actions.
  4. Save. The cybo can now use that toolkit, acting as the identity bound at run time (your account for caller runs, the shared account for service/unattended runs).

Troubleshooting

  • "Invalid API key" — the key was mistyped or revoked; regenerate it in Composio and re-save.
  • A toolkit stays "Not connected" — the OAuth popup was closed or blocked; retry and allow popups for Cyborg7.
  • A cybo can't see a tool — the toolkit is connected but not granted to that cybo (Step 4), or the run needs a service identity it doesn't have.