Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: OAuth 2.0.
  • Connection: A user authorizes the connection in the provider’s consent screen.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration. These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.

​
Setup

  1. Create an Intercom app: Sign in to Intercom and open the Developer Hub (https://developers.intercom.com/ → Your apps). Create a new app - use a development workspace for testing.
  2. Enable OAuth and set the redirect URL: In the app’s Authentication page, click Edit, enable ‘Use OAuth’, and add your redirect URL ending in /api/auth/intercom/callback.
  3. Select permissions: On the same Authentication page, tick the permissions the tools need: read/write contacts, read/list conversations, reply to conversations, and read articles. Permissions are configured here, not via OAuth scopes.
  4. Copy credentials and verify: Copy the Client ID and Client Secret from Basic information into INTERCOM_CLIENT_ID and INTERCOM_CLIENT_SECRET, connect your workspace, and run the List Contacts tool.

​
Provider notes

  • Intercom access tokens are long-lived: they do not expire and no refresh tokens are issued; reauthorize to rotate
  • Permissions are configured on the app in the Developer Hub; the authorize URL carries no scope parameter
  • Requests default to the API version pinned on your app; you can override per-request with the Intercom-Version header
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as intercom__list_contacts with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.