At a glance
- Availability: Experimental (how to enable).
- Auth: OAuth 2.0.
- Connection: A user authorizes the connection in the provider’s consent screen.
- Docs: https://developers.intercom.com/docs/build-an-integration/learn-more/authentication/setting-up-oauth
Credentials
Set these per environment. See Connect an integration. With a managed OAuth app, Connect works without these variables; set them to use your own OAuth app instead.Setup
- 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.
- 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.
- 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.
- 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.
- 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
Tools
Example prompts
- List the most recent Intercom conversations and summarize what customers are asking about.
- Search Intercom for a contact by email and show their profile.