Integrations · CRM

Connect Clarify to Well

Name: Clarify entities in Well
Creator: Well

Enrich Clarify account, deal, and contact with payment, support, and product context from your connected tools.

What Well pulls from Clarify

Clarify feeds account, deal, contact into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Clarify’s access.

From Clarify	In Well	Relation
Account	Customer	Enriches with
Deal	Revenue forecast	Feeds
Contact	Person	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Clarify → Well

What Well does with your Clarify connection

Connect

Connect Clarify over OAuth (MCP DCR): Well registers a client through Clarify's OAuth Dynamic Client Registration and you approve on Clarify's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings account, deal, and contact in from Clarify 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 Clarify entity into customer, revenue forecast, and person, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from Clarify lands in the workspace as customer, revenue forecast, and person you can search, chart, and automate.

Questions Clarify unlocks

Ask in plain language. Well answers from your connected Clarify connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Clarify connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Clarify connection…

Connect Clarify in three steps

01
Authorise Clarify via MCP
From Well's Connections panel, search for Clarify and click Connect. Well discovers Clarify's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Clarify's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP serverapi.clarify.ai/mcp
02
Map your entities
Well's MCP client discovers account, deal, and contact from Clarify that Clarify'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 Clarify records. Because Clarify 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 Clarify records happens in the background.

How Clarify stays secure with Well

Well connects to Clarify's MCP server (api.clarify.ai/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Clarify secret. Tokens are scoped to the account, deal, and contact Clarify exposes and refreshed server-side. Reads only, Well cannot modify or delete Clarify records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsapi.clarify.ai/mcp

Read Clarify records
Resources the Clarify MCP server exposes, scoped by your OAuth approval.
granted
Resolve account, deal, and contact across your stack
Match identifiers in Clarify against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Clarify records
Not granted; Clarify is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Clarify passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Clarify’s admin panel.

Frequently asked questions about Clarify and Well

From Well, open Connections, find Clarify, and click Connect. Well discovers the OAuth metadata at api.clarify.ai/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Clarify's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in account, deal, and contact from Clarify and reshapes each entity into your workspace: account becomes customer; deal becomes revenue forecast. Every record arrives with the source identifier preserved, so Clarify stays the source of truth while Well lets you query the data alongside the rest of your stack.

Well runs entity resolution across Clarify 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.

Yes. Clarify contacts are indexed in your workspace as person, so questions like "show me last week's contacts from Clarify" return them with the original Clarify link, the workspace context, and any related records (counterparty, period, attached document) joined inline.

Well combines live Clarify events with periodic reconciliation reads of account, deal, and contact. New rows appear within seconds when Clarify pushes them; periodic reads catch anything a push missed. The first connect backfills history from Clarify in the background.

Open Connections > Clarify in Well and click Disconnect. Well calls Clarify's token revocation endpoint and stops calling Clarify immediately on its side; provider-side propagation to Clarify's admin panel varies by provider. The account, deal, and contact Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

Clarify 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.