Integrations · CRM

Connect ZoomInfo to Well

Enrich ZoomInfo company record, contact, and intent signal with payment, support, and product context from your connected tools.

What Well pulls from ZoomInfo

ZoomInfo feeds company record, contact, intent signal into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke ZoomInfo’s access.

From ZoomInfoIn Well
Company record
Account enrichment
Contact
Person
Intent signal
Lead score input
ZoomInfo logo
Sync mode
MCP hybrid
Refresh
live + reconciliation reads
Direction
ZoomInfo → Well

What Well does with your ZoomInfo connection

Connect

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

Sync

Well brings company record, contact, and intent signal in from ZoomInfo 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 ZoomInfo entity into account enrichment, person, and lead score input, assigns categories, and links every record to an audit trail across the rest of your connected tools.

Available

Your data from ZoomInfo lands in the workspace as account enrichment, person, and lead score input you can search, chart, and automate.

Questions ZoomInfo unlocks

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

Ask Well

Ask anything about your ZoomInfo connection

Summarise this month
What needs attention?
Find unmatched records

Ask about your ZoomInfo connection…

Connect ZoomInfo in three steps

  1. 01

    Authorise ZoomInfo via MCP

    From Well's Connections panel, search for ZoomInfo and click Connect. Well discovers ZoomInfo's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on ZoomInfo's side. No client credentials to paste.

    • AuthOAuth (MCP DCR)
    • DiscoveryMCP .well-known
    • MCP servermcp.zoominfo.com/mcp
  2. 02

    Map your entities

    Well's MCP client discovers company record, contact, and intent signal from ZoomInfo that ZoomInfo'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
  3. 03

    Use the data

    Ask questions in conversation, build records tables, or let agents act on ZoomInfo records. Because ZoomInfo 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 ZoomInfo records happens in the background.

How ZoomInfo stays secure with Well

Well connects to ZoomInfo's MCP server (mcp.zoominfo.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 ZoomInfo secret. Tokens are scoped to the company record, contact, and intent signal ZoomInfo exposes and refreshed server-side. Reads only, Well cannot modify or delete ZoomInfo records.

OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policy
Scopes Well requestsmcp.zoominfo.com/mcp
  • Read ZoomInfo records

    Resources the ZoomInfo MCP server exposes, scoped by your OAuth approval.

    granted
  • Resolve company record, contact, and intent signal across your stack

    Match identifiers in ZoomInfo against the same entities your other connected tools expose, so each record carries cross-tool context.

    granted
  • Modify or delete ZoomInfo records

    Not granted; ZoomInfo is read-only in Well. Write-back is opt-in per connector when a write surface exists.

    refused
  • Store ZoomInfo passwords or session cookies

    Authentication runs through OAuth (MCP DCR) tokens we never see.

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

Frequently asked questions about ZoomInfo and Well

From Well, open Connections, find ZoomInfo, and click Connect. Well discovers the OAuth metadata at mcp.zoominfo.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 ZoomInfo's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in company record, contact, and intent signal from ZoomInfo and reshapes each entity into your workspace: company record becomes account enrichment; contact becomes person. Every record arrives with the source identifier preserved, so ZoomInfo stays the source of truth while Well lets you query the data alongside the rest of your stack.

Every ZoomInfo 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 company 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 account enrichment. Edits flow in incrementally; nothing is duplicated, and the ZoomInfo source identifier is retained on every revision.

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

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

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

ZoomInfo logo

Ready to connect ZoomInfo?

Connect once. Every company record, contact, intent signal from ZoomInfo becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.