Skip to main content
Real work happens inside apps — your CRM, your project tracker, your knowledge base, your code repos. Integrations connect those apps to your assistant so it can act through them: look up a customer in HubSpot, file a Jira ticket, update a Notion page, check a GitHub pull request. This all lives in the Integrations tab (the plug icon) on your assistant’s page in the Console — the home of everything your teammate can act through: mail, calendar, CRM, and more. The tab is built around a simple loop: browse the catalog (search or filter to find an app), review permissions (open a card to see exactly what the teammate would access), and connect (authorize with OAuth or paste an API key). Connecting takes under a minute and costs nothing — there are no credit charges for integrations. Each assistant has its own Integrations tab and its own connections — connecting HubSpot to your reporting teammate doesn’t connect it to anyone else. Shared access flows through teams when you want it.

​
What connecting an app unlocks

Once an app is connected, you just ask in plain language:
  • “Any new HubSpot leads since Friday?”
  • “Create a Linear issue for the login bug and assign it to Sam.”
  • “Summarize what changed in the Notion project doc this week.”
  • “Post the weekly numbers to the #metrics channel.”
Your assistant translates the request into the right actions in the right app — governed by permissions you control, with confirmation required for sensitive changes.

​
The kinds of apps you’ll see

Every app card in the gallery is labeled with its type:
  • Third-party — the broad catalog of SaaS apps (CRM, project management, files, engineering tools, and more). You connect these yourself with a sign-in or an API key.
  • Native — integrations built and operated by the platform, often tailored for a specific organization. These show a View button rather than Connect — they’re enabled as part of your deployment.
The catalog varies by organization, and it’s large — search is the fastest way to find out whether an app is supported. If something you need isn’t there, your assistant can often still work with it (see Using connected apps).

​
How integrations relate to everything else

The platform draws clear lines between three things that all involve “connecting accounts”: One example that trips people up: Slack appears twice, wearing different hats. Connecting Slack as a communication channel lets your assistant chat in your workspace as itself. Connecting Slack in the Integrations gallery lets your assistant act in your Slack account — reading channels, posting as part of automations. You can use either or both.

​
What’s in this section

Connecting apps

The gallery, OAuth and API-key flows, account labels, and multiple accounts.

Permissions & security

Per-tool permissions, approval for sensitive actions, and how credentials are protected.

Using connected apps

Asking in plain language, recurring tasks, and apps that aren’t in the gallery.