Connecting an integration

Connecting an integration is a two-minute job: open the directory, pick the connector, sign into the third-party app, come back. This article walks the flow and the few choices that matter.

Open the directory

Settings → Integrations. The grid shows every connector grouped by category, with filter chips along the top (Communication, Productivity, CRM & sales, and so on). Use the search field if you know what you're looking for; otherwise the Recommended sort surfaces the ones most workspaces start with.

Each card shows the connection state at a glance:

Not connected. Available to connect.
Connected (green). Already wired up — either to you personally or to the workspace.
Available. Connected for one scope but not yet usable for this one (e.g. workspace has Slack, but you haven't enabled it for your agents).

Open the connector

Click any card and the detail dialog opens. It has three things worth reading before you connect:

What this integration does. A short description of the connector's capabilities.
The action list. Every specific tool the integration exposes — "Read message," "Post message," "List channels," etc. This is what your agents will be able to call.
The scope picker. Connect for just me or for the whole workspace (where supported). Workspace scope needs admin rights.

Pick the right scope

The choice you'll make most often:

Just me. Right for personal accounts — your inbox, your calendar, your personal Notion. Only your agents will use it; teammates won't see the connection.
The whole workspace. Right for shared accounts — the team Slack, a shared GitHub org, a company HubSpot. Every member's agents can use it. Admins only.

Some connectors only support one scope (Gmail is typically personal; a shared support inbox would be workspace). The dialog tells you which scopes are allowed; if the workspace option is disabled, your role doesn't permit it or the connector doesn't support it.

Click Connect and a new window opens to the third-party app's sign-in. Approve the scopes the app asks for, then close the window — the dialog detects the success and flips the card to Connected.

The first connect for a fresh workspace can take a few seconds while the auth handshake completes. If the window closes without a confirmation, click Reconnect in the dialog and try again — usually a pop-up blocker or a stale browser session.

Disconnect

To stop using an integration, open its card from Settings → Integrations and click Disconnect. Two things happen:

The connection is removed from Claos. Agents lose access immediately — the next time one tries to call a tool from this integration, it'll see "not connected" and adapt.
The third-party app keeps record of having granted access until you revoke it on their side too. Disconnect in Claos is the local off-switch; the full off-switch is also revoking the OAuth grant in the third-party app's settings (Google account, Slack workspace, Notion, etc.). For routine cleanup the local disconnect is enough; for security-sensitive cases revoke on both ends.

Tips and gotchas

The "Available" state is a half-step. Workspace connected the integration, but you haven't enabled it for your agents yet (or vice versa). Open the card and complete the second step.
Reconnect isn't the same as disconnect-then-connect. Reconnect refreshes the OAuth token without dropping the connection — use it when an agent reports the connection has expired. Use Disconnect when you actually want to remove access.
Scopes are app-specific. Two connectors for the same product can request different scopes. Read what each one asks for at sign-in time; don't assume the second connection inherits the first's permissions.