Connections are reusable authenticated links to external systems. They let an agent use Gmail, GitHub, Notion, Slack, a custom OAuth provider, or an API-key-backed system without putting raw credentials into prompts or logs. A connection is scoped to an organization or fleet. After the user authorizes the provider, your app attaches the connection to an agent, optionally with metadata that helps identify the account in the UI or during tool discovery. Tool execution only considers connections attached to the current agent. If exactly one eligible connection exists, the runtime can select it automatically. If multiple eligible accounts match, discovery surfaces them as separate entries with account labels so the model can choose deliberately. Use connections when a tool should act as the end user. Use tool-owned auth when every agent should call the same backend identity. Keeping that distinction explicit makes account selection auditable and easier to reason about. To track when accounts are linked or unlinked, subscribe to theDocumentation Index
Fetch the complete documentation index at: https://docs.cerca.dev/llms.txt
Use this file to discover all available pages before exploring further.
connection.attached and connection.detached webhook events.