Concepts
Connector
An authenticated connection to a third-party app that agents and flows can act on.
What a connector is
Connectors are the pod’s hands: connect Salesforce, GitHub, or Notion once, and agents can read and act on them — within the operations you allow. Surfaces bring work in; connectors let the pod act out in your other tools.
For example
Connect Salesforce and the sales agent updates opportunity stages instead of just telling you to.
Reach for it when
- Agents or flows should act in Salesforce, GitHub, Notion, Gmail — not just talk about them.
- The pod needs to read state that lives in another product.
- A workflow step ends with "…and then update it in the other system."
Give the pod hands
- Open Connectors and connect the app with the account that should act.
- Decide the account mode: each user acts as themselves, or one fixed service account.
- Grant the connector to the specific agents and functions that need it.
- Test one real operation from a conversation before trusting it in a flow.
Where it lives
Connectors in the left sidebar; connected accounts are workspace-wide.
Related concepts
| Concept | In short |
|---|---|
| Surface | A place where work reaches the pod: Slack, Gmail, WhatsApp, Telegram, Teams, Outlook. |
| Agent | An AI worker with a role, instructions, and scoped access to your tables, files, and apps. |
| Sharing | Who can see and use a resource: private, pod members, or the whole organization. |