Integrations · CRM

Connect Attio to Well

Name: Attio entities in Well
Creator: Well

Sync CRM contacts, companies, deals, and notes from Attio to enrich your business context with customer relationship data.

Connect AttioSee what Well does

What Well pulls from Attio

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

From Attio	In Well	Relation
Company	Customer	Enriches with
Person	Contact	Resolves to
Deal	Revenue forecast	Feeds
Note	Audit trail	Appends to

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

4 triggers from Attio.

When a company record is created in Attio
Pulls the new Attio company record with its name, domain, and the attributes your workspace tracks, and matches it into your Well company graph.
Trigger·Company
When a company record is updated in Attio
Picks up edits to an Attio company's name, domain, or custom attributes and refreshes the matching Well company.
Trigger·Company
When a person is added to an Attio record
Captures the person's name, email, and role from Attio and links them to the parent company in your graph.
Trigger·Company
When a record is added to an Attio list
Reads the record added to a tracked Attio list so the company or contact it represents is brought into Well.
Trigger·Company

What Well does with your Attio connection

Connect

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

Sync

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

Available

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

Questions Attio unlocks

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

Ask Well

Ask anything about your Attio connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Attio connection…

Connect Attio in three steps

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

How Attio stays secure with Well

Well connects to Attio's MCP server (mcp.attio.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 Attio secret. Tokens are scoped to the company, person, deal, and note Attio exposes and refreshed server-side. Reads only, Well cannot modify or delete Attio records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.attio.com/mcp

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

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

Frequently asked questions about Attio and Well

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

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

Well runs entity resolution across Attio 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 customer built from Attio carries the source company identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Attio record; from Attio, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

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

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

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