Skip to main content
Open your assistant’s Integrations tab to see the app gallery. It’s organized into three sections:
  • Connected apps — everything already wired up, pinned at the top and ready for your assistant to use.
  • Needs attention — apps that need a reconnect or configuration update before they’ll work again.
  • Available apps — the full catalog, scrolling below.
Use the search box or the filters — status (Connected, Needs attention, Not connected) and type (Native, Third-party) — to narrow things down, and check the footer for the running tally of what’s connected. Each card wears badges telling you how it authorizes (OAuth, API key) and how many tools it brings.

​
Connecting an app

1

Open the app's card

Click a card to see the details before connecting: a description, the access scopes the app will ask for, and the full list of tools your assistant would gain — so you know exactly what you’re granting.
2

Click Connect and label the account

You can add an optional label so the account is easy to recognize later — “Work Slack”, “Personal Gmail”, “Client Discord”. Labels matter most when you connect more than one account to the same app.
3

Authorize

How you authorize depends on the app:
  • OAuth — a new tab opens with the app’s own sign-in page. Approve, and you’re returned to the Console.
  • API key — paste the key (or keys) into a short form; the connection is live immediately.
Right after connecting, the app’s tools take a moment to sync — your assistant will mention if they’re still warming up (“Slack tools are syncing and will be available shortly”) and again when they’re ready.
Not sure how to get an API key, or where an app’s settings live? Ask your assistant. Guiding you through app setup — ideally on a screen-share call — is one of the things it does best. Credentials are never shared through chat; everything sensitive goes through the Integrations tab.

​
Multiple accounts per app

You can connect the same app more than once — a work HubSpot and a client HubSpot, say. Each connected account:
  • has its own label (rename any time),
  • has its own tool permissions (see Permissions & security),
  • can be tested, reconnected, or disconnected independently.
Use Add account in the app’s detail view to connect another.

​
Keeping connections healthy

Each account row shows its health — Healthy or Needs attention — and you can hit Test any time to check a connection. The card and account badges tell you exactly where things stand: Disconnecting removes the authorization for that assistant; you can reconnect later if you need the app again. For apps connected with your own OAuth app credentials, disconnecting keeps the client details saved so reconnecting is one click.

​
Bring your own OAuth (admins)

Most OAuth apps connect with platform-managed credentials — click Connect and go. For organizations that want more control, each app’s detail view has a Bring your own OAuth section (admin-only) where you can register your organization’s own OAuth app instead. Reasons to bother:
  • Your branding on the consent screen — people authorizing see your organization’s app, not a generic one.
  • Custom scopes — request exactly the permissions your workflows need.
  • Apps without managed credentials — a few catalog apps can only be connected this way. Their cards say so (“Custom OAuth app required”) and stay unconnectable until an admin sets one up.
Setup is two steps: copy the authorized redirect URI shown in the Console into your provider’s developer portal, then paste in your app’s client ID and secret. The client secret is stored in the provider’s secure vault — never by the platform itself — and the configuration can be removed again at any time. For services the gallery doesn’t cover, there’s a Custom secret option: store any key/value credential (like stripe/prod/API_KEY) with your assistant, and it can use that credential to work with the service’s API directly. See Using connected apps for how that plays out in practice.