Connect an integration
How Cyborg7 integrations work — capability vs identity, personal vs shared connections — and where to connect each one.
Integrations let a cybo act in your other tools — read a Gmail thread, post to a Slack channel, move a Jira ticket. Cyborg7 brokers them through Composio, so connecting an account is the same short flow everywhere: pick the toolkit, authorize it, and (optionally) grant a cybo the right to use it.
Two things to understand first
Cyborg7 keeps capability and identity separate:
- Capability — which toolkits and actions a cybo is allowed to use. This lives on the cybo and is set by a workspace admin. It carries no credentials.
- Identity — whose account a run acts as:
- Personal (caller) — the run uses your own connected account. This is the default and the safe choice for personal inboxes/chats.
- Shared (service) — the run uses a workspace-owned account. Admin-only, and required for unattended runs (scheduled jobs, webhooks) where there is no human to act as.
So "connecting Gmail" can mean connecting your Gmail (personal) or a shared workspace mailbox (service) — the steps are the same, only who owns the connection differs.
Where to connect
Composio toolkits are connected from a cybo's editor → Tools, not from Settings → Integrations. (That page holds Cyborg7's own workspace-level integrations — GitHub, Slack, Jira, ClickUp and Chrome — and no Composio toolkits at all.)
- Open the cybo that needs the toolkit and go to its Tools step.
- Find the toolkit (Gmail, Slack, Jira, …) and choose Connect.
- Pick Personal (your account) or, if you're an admin, Shared workspace account.
- Complete the provider's OAuth screen in the popup and approve the requested scopes.
- Back in Cyborg7 the toolkit shows Connected.
Or just ask the cybo. It can tell you which toolkits it already has, whether your account is connected to each, and what is blocking the ones that don't work yet.
Let a cybo use it
A connection alone doesn't give a cybo access. Someone who can edit the cybo still grants the toolkit to it in its Tools step. A cybo can only ever use toolkits it has been granted, acting as the identity bound for that run — and only that toolkit's read actions, up to a per-toolkit cap. See what a grant covers.
Per-integration guides
- Composio — the broker that powers the others
- Slack
- Google / Gmail
- Jira
- ClickUp