Intercom

Pathbound connects to Intercom over OAuth and performs a read-only sync of your Intercom contacts, companies, and conversations into your Pathbound workspace. They’re unified with data from your CRM, website analytics, and email into a single profile per contact and company — so an AI agent or a human sees the full support history inline with everything else you know about a customer.

Pathbound never writes to Intercom. It only reads.

Conversations are attributed to the matching unified contact and surfaced on that contact’s timeline and conversation history.

Pathbound requests read access only to your Intercom workspace:

• Read contacts — to build unified contact profiles and attribute activity.
• Read companies — to roll contacts up to company-level intelligence.
• Read conversations — to show support history inline in each profile.

No write permissions are requested, because Pathbound only reads from Intercom. All writes happen in Pathbound’s own database, never back into Intercom.

1. In the Pathbound app, open Integrations and select Intercom (under Sources).
2. Click Connect Intercom. You’ll be redirected to Intercom’s secure OAuth screen.
3. Sign in to Intercom (if you aren’t already) and choose the workspace you want to connect.
4. Click Authorize. Intercom redirects you back to Pathbound, and the integration shows as Connected with the timestamp of the connection.

That’s it — no API keys to copy, no configuration. Pathbound begins syncing on the next scheduled run.

• Poll-based. Pathbound calls the Intercom API on a schedule; there are no webhooks to configure on your side.
• Incremental. After the first full sync, only contacts and conversations updated since the last run are re-fetched, so ongoing syncs are fast and light on your rate limit.
• Conversation detail fills in over time. New conversations appear as stubs within minutes; their full message threads are fetched in the background across subsequent runs.
• Non-destructive linking. When a contact is matched to a company, Pathbound fills in the association only if one isn’t already set from another source — it never overwrites.

The first full sync of a large workspace can take a while to complete; conversation threads continue to backfill in the background after contacts and companies are in place.

Once synced, open any contact in Pathbound:

• Intercom conversations appear in the contact’s conversation history and on the timeline.
• Intercom contact and company attributes enrich the unified profile alongside your other sources.

The same data is available to AI agents through Pathbound’s MCP server and REST API.

• The access token Intercom issues is encrypted at rest.
• Pathbound is read-only against Intercom — it can never modify your Intercom data.
• All data is scoped to your tenant and isolated from other Pathbound customers.
• See our Privacy Policy and Terms of Service.

To stop the sync and revoke access:

1. In the Pathbound app, open Integrations → Intercom.
2. Click Disconnect.

Disconnecting deletes the stored Intercom access token from Pathbound. You can also revoke Pathbound’s access from within your Intercom workspace settings at any time.

• Stuck on “Connecting” / error after authorizing. Start the flow again from Integrations → Intercom → Connect Intercom. OAuth state expires after a short window, so a slow or interrupted authorization can need a retry.
• Conversations aren’t appearing. Some Intercom plans don’t include API access to the Conversations endpoint. Contacts and companies will still sync; conversation history needs a plan that exposes that API.
• A contact’s conversations are missing. Attribution waits until that contact has synced from Intercom. Give the sync a cycle or two to link the contact, and the conversations will attach.

Need help? Email [email protected].