# Intercom setup for PopMCP

You paste the Access Token that Intercom's Developer Hub issues for a private app installed on your workspace, plus the one-word data region (us, eu or au) that workspace is hosted in.

- Auth: API credentials
- Setup time: 4 min
- API base URL: https://api.intercom.io
- Credentials screen: https://app.intercom.com/a/apps/_/developer-hub/app-packages
- Provider docs: https://developers.intercom.com/docs/build-an-integration/learn-more/authentication

## Before you begin

- An Intercom workspace on any plan. The Developer Hub is free.
- A teammate account that can create apps in that workspace (Owner or Admin).
- Knowing which region hosts your workspace: US, EU or Australia.

## Get your credentials

### 1. Open the Intercom Developer Hub

Sign in to Intercom and go to app.intercom.com/a/apps/_/developer-hub. Click Your apps in the sidebar.

Screen: https://app.intercom.com/a/apps/_/developer-hub/app-packages

### 2. Create a private app for PopMCP

Click New app, type `PopMCP` in the name field, and pick your workspace from the Workspace dropdown. Click Create app.

Screen: https://app.intercom.com/a/apps/_/developer-hub/app-packages

### 3. Copy the Access Token

In the app sidebar open Configure → Authentication. Copy the value shown under Access Token.

Screen: https://app.intercom.com/a/apps/_/developer-hub/app-packages

### 4. Paste the token and region into PopMCP

Paste the token into Access token, then set Data region to `us`, `eu` or `au` to match your workspace. Leave the region blank for US.

## Fields PopMCP asks for

- Access token (accessToken) [required]: Intercom Developer Hub → Your apps → (create or open an app) → Authentication → Access token. The token carries the permissions set on that app. Stored encrypted.
- Data region (us, eu, or au) (region): Where your Intercom workspace is hosted: us (default, api.intercom.io), eu (api.eu.intercom.io), or au (api.au.intercom.io). Tokens only work against their own region's host.

## Verify

The Intercom connection flips to Connected in PopMCP and its tools appear. Listing recent conversations returns real records from that workspace.

## Troubleshooting

### 401 Unauthorized on every call

Cause: The token belongs to a workspace in a different data region than the one selected, or it was truncated when copied.

Fix: Re-copy the whole Access Token from Configure → Authentication, then set Data region to us, eu or au to match your workspace. Each region has its own host: api.intercom.io, api.eu.intercom.io, api.au.intercom.io.

### 403 Forbidden on some endpoints only

Cause: The app does not hold the permission that endpoint requires.

Fix: Open the app in the Developer Hub, tick the missing read and write permissions, save, then reconnect in PopMCP.

### No Access Token shown on the Authentication page

Cause: The app was never installed on a workspace.

Fix: Go to Test and publish → Your workspaces and click Install app next to the workspace you want. The token then appears beside it.

### The connection stopped working after someone clicked Regenerate token

Cause: Regenerating issues a new Access Token and invalidates the old one.

Fix: Copy the new token from Configure → Authentication and update the PopMCP connection.

---

Source: https://www.docs.popmcp.com/docs/integrations/intercom/