Skip to main content
For services with one-click OAuth, connecting is a single authorize and you are done. Skydive handles token refresh automatically, so the connection keeps working without re-authorizing. This is the preferred method for account-level access when the service supports it. Check the catalog to see which method a service offers. For services with one-click OAuth, connecting is a single authorize and you’re done. The platform handles token refresh automatically, so the connection keeps working without re-authorizing.
1

The agent requests a connection

Either you set it up from the catalog ahead of time, or the agent prompts you with a connect card when it hits a task that needs it.
2

A connect card appears

Click it, sign in with the provider, and approve the scopes.
3

You're connected

The agent can now act in that service securely, through the proxy.

​
Per-item grants

Some providers scope the grant to items you pick on the consent screen. Notion is the clearest case: the token sees only the pages you selected, plus their children. With one of these, an empty search result usually means “not shared with this connection” rather than “does not exist”. Two fixes: share the item with the connection inside the provider, or re-run the connection to reopen the consent screen and widen the selection. Re-running renews the connection in place, and the existing grant keeps working until the new authorization completes.

​
Managing a connection

Once a service is connected, manage it from the integration’s card in your workspace. The card shows which agents use the connection and gives you two options to pull access back:
  • Remove from one agent. The connection stays live for your other agents.
  • Disconnect entirely. This revokes Skydive’s access at the provider and removes it from every agent using it.

Catalog

Every service available to connect.

Permissions

How credentials stay out of the model’s reach.