Connect Common Room to Well
Enrich Common Room community signal, member, and channel with payment, support, and product context from your connected tools.
What Well pulls from Common Room
Common Room feeds community signal, member, channel into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Common Room’s access.
| From Common Room | In Well | Relation | |
|---|---|---|---|
| Community signal | Engagement record | Becomes | |
| Member | Person | Resolves to | |
| Channel | Workspace context | Groups under |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Common Room → Well
What Well does with your Common Room connection
Connect
Connect Common Room over OAuth (MCP DCR): Well registers a client through Common Room's OAuth Dynamic Client Registration and you approve on Common Room's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings community signal, member, and channel in from Common Room 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 Common Room entity into engagement record, person, and workspace context, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Common Room lands in the workspace as engagement record, person, and workspace context you can search, chart, and automate.
Questions Common Room unlocks
Ask in plain language. Well answers from your connected Common Room connection, resolved against the rest of your stack.
Ask anything about your Common Room connection
Ask about your Common Room connection…
Connect Common Room in three steps
- 01
Authorise Common Room via MCP
From Well's Connections panel, search for Common Room and click Connect. Well discovers Common Room's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Common Room's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.commonroom.io/mcp
- 02
Map your entities
Well's MCP client discovers community signal, member, and channel from Common Room that Common Room'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 Common Room records. Because Common Room 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 Common Room records happens in the background.
How Common Room stays secure with Well
Well connects to Common Room's MCP server (mcp.commonroom.io/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Common Room secret. Tokens are scoped to the community signal, member, and channel Common Room exposes and refreshed server-side. Reads only, Well cannot modify or delete Common Room records.
- granted
Read Common Room records
Resources the Common Room MCP server exposes, scoped by your OAuth approval.
- granted
Resolve community signal, member, and channel across your stack
Match identifiers in Common Room against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Common Room records
Not granted; Common Room is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Common Room passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Common Room and Well
From Well, open Connections, find Common Room, and click Connect. Well discovers the OAuth metadata at mcp.commonroom.io/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Common Room's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in community signal, member, and channel from Common Room and reshapes each entity into your workspace: community signal becomes engagement record; member becomes person. Every record arrives with the source identifier preserved, so Common Room stays the source of truth while Well lets you query the data alongside the rest of your stack.
Well runs entity resolution across Common Room contacts and accounts using identifier overlap, email-domain matches, company-name normalisation, and prior workspace entities. Contacts that should belong to the same person collapse onto one workspace identity; accounts that should belong to the same parent company resolve to one workspace company.
Every workspace engagement record built from Common Room carries the source community signal identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Common Room record; from Common Room, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.
Well combines live Common Room events with periodic reconciliation reads of community signal, member, and channel. New rows appear within seconds when Common Room pushes them; periodic reads catch anything a push missed. The first connect backfills history from Common Room in the background.
Open Connections > Common Room in Well and click Disconnect. Well calls Common Room's token revocation endpoint and stops calling Common Room immediately on its side; provider-side propagation to Common Room's admin panel varies by provider. The community signal, member, and channel Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Common Room 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 Common Room
More in CRM
Popular cross-category
Ready to connect Common Room?
Connect once. Every community signal, member, channel from Common Room becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.