When a lead is created in Close
Pulls the new lead's company record with name, URL, and the custom fields your team tracks.
Trigger·Company
Integrations · CRMConnect Close to Well
Enrich Close company record, and person record with payment, support, and product context from your connected tools.
What Well pulls from Close
Close feeds company record, person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Close’s access.
| From Close | In Well | Relation | |
|---|---|---|---|
| Company record | Customer | Enriches | |
| Person record | Contact | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Close → Well
3 triggers from Close.
When a contact is added to a Close lead
Captures the contact's name, role, and email and links them to the parent company.
Trigger·CompanyWhen a company is updated in Close
Picks up edits to the company's name, domain, or custom fields and refreshes your graph.
Trigger·Company
What Well does with your Close connection
Connect
Connect Close over OAuth (MCP DCR): Well registers a client through Close's OAuth Dynamic Client Registration and you approve on Close's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings company record, and person record in from Close 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 Close entity into customer, and contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Close lands in the workspace as customer, and contact you can search, chart, and automate.
Questions Close unlocks
Ask in plain language. Well answers from your connected Close connection, resolved against the rest of your stack.
Ask Well
Ask anything about your Close connection
Summarise this month
What needs attention?
Find unmatched records
Ask about your Close connection…
Connect Close in three steps
- 01
Authorise Close via MCP
From Well's Connections panel, search for Close and click Connect. Well discovers Close's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Close's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.close.com/mcp
- 02
Map your entities
Well's MCP client discovers company record, and person record from Close that Close'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 Close records. Because Close 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 Close records happens in the background.
How Close stays secure with Well
Well connects to Close's MCP server (mcp.close.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 Close secret. Tokens are scoped to the company record, and person record Close exposes and refreshed server-side. Reads only, Well cannot modify or delete Close records.
OAuth (MCP DCR)Encrypted at restGDPR compliant
Read the full privacy and security policyScopes Well requestsmcp.close.com/mcp
- granted
Read Close records
Resources the Close MCP server exposes, scoped by your OAuth approval.
- granted
Resolve company record, and person record across your stack
Match identifiers in Close against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Close records
Not granted; Close is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Close passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Disconnect any time from Well settings or Close’s admin panel.
Frequently asked questions about Close and Well
How do I connect Close to Well, and how long does it take?
From Well, open Connections, find Close, and click Connect. Well discovers the OAuth metadata at mcp.close.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 Close's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
What does Well pull into the workspace from Close?
Well brings in company record, and person record from Close and reshapes each entity into your workspace: company record becomes customer; person record becomes contact. Every record arrives with the source identifier preserved, so Close stays the source of truth while Well lets you query the data alongside the rest of your stack.
How does Well enrich Close accounts with my payment, support, and product data?
Well joins each Close account or contact to the payment, support, and product records the same company has in your other connected tools. Account pages in conversation answer questions like "what did Globex pay us last quarter" by joining the Close record to invoices, tickets, and product usage in real time.
How does Well match a company record from Close to a customer in my workspace?
Each Close company record is scored against the candidate customers in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely customer prefilled and the Close source attached.
How often does Close sync with Well, and what triggers a refresh?
Well combines live Close events with periodic reconciliation reads of company record, and person record. New rows appear within seconds when Close pushes them; periodic reads catch anything a push missed. The first connect backfills history from Close in the background.
Can I disconnect Close and what happens to the data Well already pulled?
Open Connections > Close in Well and click Disconnect. Well calls Close's token revocation endpoint and stops calling Close immediately on its side; provider-side propagation to Close's admin panel varies by provider. The company record, and person record Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Where does Well store what it pulls in from Close?
Close 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 Close
More in CRM
Popular cross-category
Ready to connect Close?
Connect once. Every company record, person record from Close becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.