Connectors overview

Connect outside accounts like Slack, Notion, or GitHub so agents can use them. Linking an account and granting an agent access are two separate steps.

Connectors let agents read and act on outside accounts such as GitHub, Slack, Google, Notion, Linear, LinkedIn, and X. Connecting an account stores a credential in one workspace; agents in that workspace can then request access to it.

Workspace connections versus personal links

There are two kinds of connection, and each provider supports one or both:

• A workspace connection is made by a workspace owner or admin and belongs to the workspace, for example the workspace's GitHub installation or its Notion workspace. Admins approve which agents may use it.
• A personal link is your own account, linked by you. It stays private to you: workspace admins do not see it, and only your own private agents can ever be granted it, with your approval, in a one to one chat.

Each provider's own page describes which of the two it supports and any preconditions: GitHub connector, Slack connector, Google connector, Notion connector, Linear connector, LinkedIn connector, X (Twitter) connector, and MCP servers.

A grant is separate from a link

Linking an account does not give any agent access to it. Access always takes a second step: the agent requests a credential grant, and the right person approves it on a card in chat. For a workspace connection that approver is a workspace owner or admin; for a personal link it is you, the person who linked it. A grant can be narrower than the account, for example specific repositories or read only access, and it can be revoked at any time. Who approves and revokes each kind is covered in Connected accounts, credentials, and grants.

Links land in one workspace

An account link lives in exactly one workspace and only serves that workspace's agents. If a private agent offers you link buttons in chat, the card names the workspace the link will land in.

Where to browse and manage connections

The workspace's Integrations tab has two views, and it opens on the first.

Browse is a catalogue of what you can connect. Search it by name, or narrow it with the category chips above the grid; a count beside them says how many integrations you are looking at. A card starts that connection when you press it, and reads Connected once the workspace has it. If you are a member rather than an owner or admin, the cards you can press are the ones you could already link: your own personal accounts, such as LinkedIn and X, and the connectors that offer you a personal lane, such as Notion and Linear. A connector that only comes as one connection for the whole workspace, such as GitHub or Google Workspace, says Admins only instead, because those are the owners' and admins' to make. The last tile in the grid, Connect any MCP server, is for a tool the catalogue does not list; see MCP servers.

Connected lists what this workspace has already linked, plus your own personal links, and is where you manage one: reconnect it, see the agents that hold a grant on it, and remove it.

Connecting from either view is still only the first step. The grant is separate, as above. Agents can also hand you a one tap link button in chat for providers that support it; see How account linking flows work.