Connecting integrations
Integrations live in Connections (sidebar → Connections, or Settings → Project Settings → Connections). Each integration is scoped to a single project — connecting HubSpot in Project A does not connect it in Project B.
OAuth flow — most integrations use OAuth. Click Connect, a popup opens, you authorize the Magister app in the provider's UI, and control returns here. The token is stored server-side.
API key flow — a few integrations (Ahrefs, Instantly, parts of PostHog, etc.) use API keys instead. You'll be prompted to paste a key. Keys are encrypted at rest before being stored.
Where credentials live — OAuth tokens and API keys are stored in the gateway, encrypted, and only decrypted when the agent makes a request to that provider on your behalf. They're never stored in the chat transcript.
"Start a new chat to use it" — after connecting a new integration, Magister may prompt you to start a new chat. This is because the agent's capability list is computed at the start of a session; a new session picks up the new integration immediately.
Disconnecting — click Disconnect on any connected service. This revokes Magister's access (as much as the provider's API allows) and deletes the token from our storage. The agent won't be able to call that provider anymore until you reconnect.
Who can connect — anyone with access to the project can open Connections and connect or disconnect integrations. If your team wants to restrict this to admins, scope project membership accordingly. See Roles.