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