Integrations¶
The agent's Integrations settings are where you connect it to outside accounts and channels. Connecting each one gives the agent new tools that act on your behalf. Any installed skill that needs credentials also appears here, showing Connected or Not configured so you can configure or disconnect it.
Google Workspace¶
Connect Google so the agent can work with Calendar, Sheets, Docs, and Drive. For each service you choose an access level:
- Off — the agent can't use it.
- Read — read-only access.
- Read & write — full access.
You also choose a connection mode:
- Each user connects their own Google account — every end user links their own Google account, and the agent acts on that person's data, in chat and in the workflow runs that act as them. Each user connects (or picks an existing account from their library) in the agent's setup window, opened from the chat — or from Run, when a workflow needs it — and if someone starts using a Google-powered action before connecting, the agent also offers a connect button right in the chat — so no one has to be told where to go.
- One shared account — you connect a single Google account once, and the agent uses it for everyone who talks to the agent and for every workflow run.
You enable the integration, pick the services and levels, and either save (so end users connect from the agent's setup window or in chat) or Save & connect Google for the shared-account mode. In per-user mode, you can also connect your own account from this panel — handy for testing the integration as an end user of your own agent; to remove it, use Manage in Connections. You can see how many users have connected, edit the service selection, or disable the integration. Connecting and disconnecting happen through Google's own sign-in screen.
In workflows. A workflow step can use the same Calendar, Sheets, Docs and Drive access this panel grants — reading a sheet, adding rows, creating an event — within the level you set for each service here: Read for a step that reads, Read & write for one that writes. A workflow run acts as a person — whoever pressed Run, asked the agent in chat, or set up the schedule or webhook that started it (see Whose run it is) — and its Google steps work on that person's access. With One shared account, every run uses the one account you connected; in per-user mode the workflow's Google steps use the Google account of the person the run acts as, who connects it in the agent's setup window before their first run. The levels you set here apply to every run, whoever it acts as: a person's own account can't give a step more than Read where you chose Read. You can connect Google before or after the workflow is built — the Builder builds the step either way, and the first run tells you if anything here still needs setting. In the shared-account mode the form's button is Save & connect Google even once the account is connected: when a level you raise needs access the account hasn't granted yet, saving opens Google's own screen to approve it. Until you approve it there, the panel shows Google hasn't approved the new access yet. with an Approve in Google button, and a run that needs the new access doesn't start until you do. Picking a different Google account from your library in the form saves without opening Google; if that account hasn't granted the access yet, the panel shows the same notice and button. Spreadsheet values a workflow writes are written as text by default — a cell beginning with = is stored as those characters — and a single step can be allowed to write live formulas; see Steps that write into a spreadsheet.
Mailbox¶
Give the agent a mailbox over IMAP/SMTP so it can read, search, reply to, and send email. You choose whose mailbox it uses:
- Each user connects their own — every person who uses the agent connects their own mailbox, and the agent reads and sends from their mailbox in chat; a workflow run that acts as them sends from it too. This is the default for v2 agents. People connect it in the agent's My settings → Connections, or pick a mailbox already in their Connections library.
- Shared — my connection for everyone — the agent uses your mailbox for everyone who talks to it. Everyone can read your inbox and send as you, so use this only when that is what you want.
In workflows. An Agent step can use this same mailbox: list and read messages, search them, mark one as read, reply, send a new message, and forward one. A reply or a new message can include files the run already has, and reading a message can bring back an attachment. Forwarding sends the original message's text. With Each user connects their own, the run uses the mailbox of the person it acts as; with Shared — my connection for everyone, every run uses yours. On the workflow diagram the step shows the kind of account and the address, such as Email — Gmail. A step that only needs to send one prepared message — a morning report, an alert — is a Notify step instead. That mail goes out from the platform mailbox, or from a mail server you set on the step, not from this account.
To add a mailbox, a two-step wizard lets you pick your email provider (for popular providers the server addresses are pre-filled, and it points you to where to get an app password), enter the address and app password, optionally set a display name, and expand Advanced server settings for IMAP/SMTP hosts and ports. The mailbox is checked with the server before it is saved and lands in your Connections library, so other agents can reuse it. From the agent's Integrations panel you can switch the mode, pick which of your mailboxes the agent uses, Test it, or remove the mailbox from the agent (the connection stays in your library).
Telegram¶
Connect a Telegram bot and chat so the agent's workflows can send notifications to Telegram. Create a bot via @BotFather, then enter the bot token and the chat ID; the token is checked with Telegram before it is saved. By default notifications go to your chat whoever runs the workflow; switch the mode to Each user connects their own to send each person's runs to their own chat — each person then connects their own bot and chat in the agent's setup window, and their runs of a workflow that notifies Telegram don't start until they have. Telegram is a notification channel only — the agent does not read or answer Telegram messages.
Availability by deployment
Google and Telegram integrations can each be switched off at the deployment level, in which case they won't appear for agents on that deployment. This is a per-installation setting, not a per-agent one.
Connections library¶
On iPhone, open Settings → Connections → + → Google account to add a Google account to your library. The add menu closes before Google's sign-in screen opens. After you approve access, the account appears in your connections list.
Your account keeps a Connections library — every MCP server, Google account, mailbox and Telegram chat you've connected, listed once each with the agents that use it. Each entry shows where it points (the Google account, the mailbox address, the bot and chat, or the server's host or package), a Test or Connect button, and a menu to rename it, update its secrets (a new app password or bot token for a mailbox or Telegram chat), unlink it from one agent or delete it. Add a mailbox or a Telegram chat to your library with Add mailbox / Add Telegram at the top of the page. Unlinking keeps the connection in your library: an agent that asks each user to connect their own will ask you to pick a connection again, and on your own agent the tool stays without credentials until you choose another connection in the agent's settings. It's the same place you land in when an agent asks you to connect or pick from your existing connections, so you can review or manage them outside of any single agent's chat.
To add an MCP server to your library, use Add → Install package or Add → Manual config — the same two ways described under Connecting external tools via MCP — or Add → With the assistant, which opens the account assistant to find and connect a server for you, including signing in via OAuth where a server needs it.
Each MCP connection has an Available in main chat toggle, on by default. Turning it on lets your main assistant use that connection in your everyday chats, not just the agents it's attached to. A shared connection of an agent that's shared or published carries a warning badge — Everyone using <agent> uses your credentials — since everyone who talks to that agent acts through your connection, in chat and in their workflow runs; if that's not what you want, switch the agent's integration to Each user connects their own so every end user connects their own instead.
For an integration set to "Each user connects their own", every end user maintains their own connection independently — connecting once in your library lets you reuse it for other agents that need the same kind of access, instead of connecting again from scratch. An integration set to "Shared (my connection)" uses the owner's single connection for everyone who talks to the agent, and for all of their workflow runs.
Personal connections and per-user environment variables require a v2 agent — v1 agents don't support them, and end users only ever see the shared-connection experience for those agents.