When a lead is created in Close
Pulls the new lead's company record with name, URL, and the custom fields your team tracks.
Bring your Close company and people records into Well to connect your sales contacts with your business context
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 |
Pulls the new lead's company record with name, URL, and the custom fields your team tracks.
Captures the contact's name, role, and email and links them to the parent company.
Picks up edits to the company's name, domain, or custom fields and refreshes your graph.
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.
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.
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.
Your data from Close lands in the workspace as customer, and contact you can search, chart, and automate.
Ask in plain language. Well answers from your connected Close connection, resolved against the rest of your stack.
Ask anything about your Close connection
Ask about your Close connection…
Well lists Close in the connection check every skill runs before it answers. No skill reads it for a figure yet.
Connects and checks Close
Authorize Well to access your Close account from the connection panel.
Confirm the connection to allow Well to read your company and people records.
Let the background sync complete to populate your workspace with your Close contacts.
Well only requires read access to your Close data and will never modify your CRM records.
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.
Read Close records
Resources the Close MCP server exposes, scoped by your OAuth approval.
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.
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.
Store Close passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Well extracts company and people records from your Close account to help build your business context.
No. Well only reads data from Close. It does not write, update, or modify any records in your Close account.
Well syncs with Close in the background to keep your company and people records updated without manual exports.
More in CRM
Popular cross-category
Connect once. Every company record, person record from Close becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.