Skip to main content
Integrations let a coworker pull in more context automatically, instead of you having to attach everything yourself. Once you connect a tool, any coworker can draw on it when it’s relevant to the task — you never have to remind them it’s there.
FigmaFigma
SlackSlack
GitHubGitHub
HubSpotHubSpot
MailchimpMailchimp
SalesforceSalesforce
MiroMiro
Microsoft TeamsTeams
FigmaFigma
SlackSlack
GitHubGitHub
HubSpotHubSpot
MailchimpMailchimp
SalesforceSalesforce
MiroMiro
Microsoft TeamsTeams
Google Search Console and Google Analytics are live and connectable today. The rest above are on the roadmap — see “What’s live vs. what’s coming” below for the current state of each.

​
Why you’d bother connecting anything

Without an integration, you’re the one copying data out of Google Search Console and pasting it into an email to Hannah. With it connected, Hannah pulls the same data herself and Alex can build a live dashboard directly from it — the value isn’t a new capability, it’s removing the manual step between “the data exists somewhere” and “a coworker can use it.”
You don’t need to connect anything to get started. Coworkers work perfectly well from what you send them directly — integrations just mean less copy-pasting for you over time.

​
Two ways to connect

Connections Hub

One-click, secure OAuth connections to services you already use — Google Search Console and Google Analytics are live today, with a growing roadmap.

Custom MCP servers

For teams with their own internal tools or data sources — up to 10 servers, a more advanced but still self-service setup.
Most people only need the Connections Hub. Custom MCP servers are for teams who want to plug in something specific to their own systems.

​
What’s live vs. what’s coming

Right now, exactly two services are connectable: Google Search Console and Google Analytics, both read-only. See the Integration Directory for the full roadmap of what’s coming next and which coworker would actually use each one — it’s worth a look even today, since it tells you what to expect rather than leaving “coming soon” as a vague promise.
“MCP” stands for Model Context Protocol — an open standard that lets a coworker safely call an external tool or data source. You’ll see the term in the console, but you never need to understand it to use a connection.

​
How this connects

A connection doesn’t belong to one coworker — once Google Search Console is connected, both Hannah and Alex can use it, each for what they’re actually good at (Hannah for SEO research, Alex for a live dashboard). See Skills for how a coworker decides what to draw on for a given task, and Credits & Billing for how integration-fed work is priced (the same as anything else).