A direct Intercom connector shows your agent Intercom. Pathbound shows your agent the customer — Intercom conversations stitched together with your CRM, Gmail, website tracker, and the rest of your stack — through one unified profile served over the Model Context Protocol.
Every Intercom conversation and message thread lands on the contact’s timeline, next to CRM records, emails, and page views — so an agent reading a profile sees the whole support history, not a separate tab.
The same person across Intercom, your CRM, and Gmail resolves to one entity. A direct connector only knows Intercom’s own contact IDs.
Pathbound only reads from Intercom — contacts, companies, and conversations. It never writes back, so connecting it can’t change your support data.
Token-efficient response shapes and server-side aggregation mean agents get the answer, not a raw conversation dump — and it stays inside the context window.
OAuth once. The sync does the rest.
Create an account at pathbound.ai. Free during public alpha.
In the dashboard, go to Integrations → Intercom → Connect Intercom. Authorize over OAuth in one click — no API keys. Pathbound requests read-only access and syncs contacts, companies, and conversations on a schedule. See the setup guide.
Intercom conversations appear on each contact’s profile in the app, and through Pathbound’s MCP server and REST API for Claude, ChatGPT, Cursor, and any MCP client.
No. The Intercom integration is read-only — it pulls contacts, companies, and conversations into Pathbound and never writes anything back to Intercom.
Intercom contacts and their attributes, companies, and conversations (including message threads), merged onto the matching unified contact and company profiles. Custom attributes come through inline.
Standard OAuth 2.0. You authorize from the Pathbound dashboard; the token is encrypted at rest, and you can disconnect anytime from Integrations → Intercom, or revoke access from within your Intercom workspace settings.
Same unified profile, same MCP tools — just connect a different source. See the integrations directory.
Sign up. Drop in the tracker snippet. Connect one CRM. Point your MCP client at
mcp.pathbound.ai/mcp.