Integrations · CRMConnect Intercom to Well
Enrich Intercom conversation, user, and company with payment, support, and product context from your connected tools.
What Well pulls from Intercom
Intercom feeds conversation, user, company into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Intercom’s access.
| From Intercom | In Well | Relation | |
|---|---|---|---|
| Conversation | Audit entry | Captures as | |
| User | Person | Resolves to | |
| Company | Customer | Enriches with |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Intercom → Well
What Well does with your Intercom connection
Connect
Connect Intercom over OAuth (MCP DCR): Well registers a client through Intercom's OAuth Dynamic Client Registration and you approve on Intercom's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings conversation, user, and company in from Intercom on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Intercom entity into audit entry, person, and customer, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Intercom lands in the workspace as audit entry, person, and customer you can search, chart, and automate.
Questions Intercom unlocks
Ask in plain language. Well answers from your connected Intercom connection, resolved against the rest of your stack.
Ask anything about your Intercom connection
Ask about your Intercom connection…
Connect Intercom in three steps
- 01
Authorise Intercom via MCP
From Well's Connections panel, search for Intercom and click Connect. Well discovers Intercom's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Intercom's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.intercom.com/mcp
- 02
Map your entities
Well's MCP client discovers conversation, user, and company from Intercom that Intercom's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Intercom records. Because Intercom ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Intercom records happens in the background.
How Intercom stays secure with Well
Well connects to Intercom's MCP server (mcp.intercom.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Intercom secret. Tokens are scoped to the conversation, user, and company Intercom exposes and refreshed server-side. Reads only, Well cannot modify or delete Intercom records.
- granted
Read Intercom records
Resources the Intercom MCP server exposes, scoped by your OAuth approval.
- granted
Resolve conversation, user, and company across your stack
Match identifiers in Intercom against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Intercom records
Not granted; Intercom is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Intercom passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Intercom and Well
From Well, open Connections, find Intercom, and click Connect. Well discovers the OAuth metadata at mcp.intercom.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Intercom's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in conversation, user, and company from Intercom and reshapes each entity into your workspace: conversation becomes audit entry; user becomes person. Every record arrives with the source identifier preserved, so Intercom stays the source of truth while Well lets you query the data alongside the rest of your stack.
Every Intercom deal carries its stage, owner, and amount into Well. Conversations can answer "which deals slipped this quarter" or "how many late-stage deals are stalled" without leaving the workspace, and downstream agents can act on the same pipeline view.
Well watches for updates to conversations and applies them on the next sync, preserving the original workspace identifier so anything downstream (records tables, conversation history, agent runs) keeps pointing at the right audit entry. Edits flow in incrementally; nothing is duplicated, and the Intercom source identifier is retained on every revision.
Well combines live Intercom events with periodic reconciliation reads of conversation, user, and company. New rows appear within seconds when Intercom pushes them; periodic reads catch anything a push missed. The first connect backfills history from Intercom in the background.
Open Connections > Intercom in Well and click Disconnect. Well calls Intercom's token revocation endpoint and stops calling Intercom immediately on its side; provider-side propagation to Intercom's admin panel varies by provider. The conversation, user, and company Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Intercom records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with Intercom
More in CRM
Popular cross-category
Ready to connect Intercom?
Connect once. Every conversation, user, company from Intercom becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.