What are integrations?

An integration is a third-party app your agents are allowed to act in. Connect one and the agent gains a new set of tools — read your Gmail, post in Slack, file a Jira ticket, fetch a Notion page, draft a HubSpot record. Without integrations the agents still work, but they're confined to the workspace; integrations are how their reach extends to the rest of your software.

The mental model

Agents have tools — actions they're allowed to take. Some of those tools touch the workspace (search pages, create tasks, comment). Others touch external apps, and that's what integrations are for. When you connect Gmail, you don't enable the integration "in general" — you give agents a new set of Gmail-shaped tools that they can use the next time they run.

Two things to keep in mind:

Integrations are inputs to the agent, not standalone features. You don't "use the Slack integration" the way you'd use a feature in Slack itself. You connect Slack, then assign or chat with an agent that knows how to use it.
Each integration is a bundle of specific actions. Connecting Gmail gives an agent the ability to read mail, draft mail, search threads — not "do anything in Gmail." The detail dialog in Settings → Integrations shows the full list of actions for each connector.

Where you meet them

Settings → Integrations is the directory. ~60+ connectors grouped by category — Productivity, Communication, CRM & sales, Project management, DevOps, Support, Marketing, Design, Research & web, Media, Social, Commerce, Legal & docs. Each card shows whether the connector is connected for the workspace, connected for just you, or available to connect.

When an agent runs and calls an integration, the tool call shows up in the run timeline the same way a workspace tool call does. If the integration isn't connected, the agent gets back a "not connected" signal and either asks you to connect it or works around the gap.

Personal vs. workspace connections

Most integrations support two scopes:

Workspace connection. An admin connects the integration once, and every member's agents can use it. Right call for shared accounts — a team Slack, a shared GitHub org, a company HubSpot.
Personal connection. You connect the integration for yourself. Only your agents see the connection; teammates don't. Right call for personal accounts — your inbox, your calendar, a personal Notion.

Some connectors only support one scope. The detail dialog tells you which scopes are allowed for that connector.

What agents actually do with them

The pattern that lands is delegation, not orchestration. You don't say "use the Gmail tool to fetch the last 10 messages from X and summarise." You say "draft me a summary of this morning's customer mail." The agent picks the right tool, calls it, reads the result, and writes the output. Integrations are the agent's hands; you brief the agent, not the hand.

A few real examples:

An agent assigned to a recurring "morning brief" task connects to Gmail and Calendar, reads what landed overnight, and writes a brief to a knowledge-base page.
A team's customer-support member connects to Zendesk and Slack, watches for new tickets, drafts replies, and pings the on-call channel for the hard ones.
A custom analyst agent connects to HubSpot and Google Sheets, pulls weekly pipeline data, and writes a status report to the team folder.

Tips and gotchas

Don't connect everything. The agent's tool list grows with each integration, and large tool lists cost the model more attention. Connect what your agents actually need; revisit when the work changes.
Per-agent toggles matter. Connecting Gmail at the workspace doesn't mean every agent will read your mail. Each agent has its own Tools & Access list — the integration only kicks in for agents you've explicitly enabled it for.
Slack as an integration is different from Slack as a channel. Slack-the-integration lets agents post and read in Slack on your behalf. Slack-the-channel lets you chat with your agents from Slack. They live on different settings pages and are separate connections. See Messaging channels.