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
Read Close leads, contacts, won opportunities, and invoices into Well through the Close MCP server. A deal closing in Close becomes a financial record, not just a pipeline status.
What Well pulls from Close
Close feeds lead, contact, won opportunity 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 | |
|---|---|---|---|
| Lead | Company | Resolves to | |
| Contact | Person | Resolves to | |
| Won opportunity | Transaction | Lands as | |
| Invoice | Receivable | Becomes |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Close → Well
6 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 Close opportunity is marked won
Reads the won opportunity's value and currency so closed revenue lands against the account.
Trigger·TransactionWhen an invoice is issued in Close
Captures the issued invoice with its line items, customer, and totals for matching.
Trigger·InvoiceWhen a Close invoice is marked paid
Detects the payment recorded against a Close invoice so the receivable can be reconciled.
Trigger·TransactionWhen 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 lead, contact, and won opportunity 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 company, person, and transaction, 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 company, person, and transaction 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 through its MCP server
Select Close in Well's Connections panel to begin. Well fetches the OAuth metadata from the Close MCP server at mcp.close.com, registers via Dynamic Client Registration, and routes you to Close to approve the read scopes. No keys to manage; you decide on Close's screen what Well may read.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.close.com/mcp
- 02
Map your entities
Well reads leads, contacts, won opportunities, and invoices, mapping leads to companies, contacts to people, and the value of a won deal to a transaction against its company through Well's data-views layer.
- Mappingpreconfigured by Well
- 03
Use the data
Then ask about revenue closed this quarter, table won opportunities by company, or let an agent join closed deals to the rest of your finances. Close stays the pipeline system of record; Well holds the financial reading of it, read-only.
- First syncstarts as soon as connect completes
Connecting takes about a minute. Pipeline records are read on connect and earlier history backfills in the background.
How Close stays secure with Well
Well talks to Close through its MCP server at mcp.close.com using the Model Context Protocol, and OAuth Dynamic Client Registration means the Close credential is never held by Well. The granted token is scoped to leads, contacts, opportunities, and invoices, and it refreshes server-side. The connection reads the pipeline; it cannot create, advance, or delete a deal in Close.
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 lead, contact, won opportunity, and invoice 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
Select Close in Well's Connections panel to begin. Well fetches the OAuth metadata from the Close MCP server at mcp.close.com, registers through Dynamic Client Registration, and sends you to Close to approve the read scopes. There are no API keys to manage, and you decide on Close's screen exactly what Well may read.
Leads, contacts, won opportunities, and invoices all cross into the workspace. A lead resolves to a company and a contact to a person, which is the part most CRM connectors stop at. Close goes further for Well because it also carries the invoice and the value behind a won deal, so a closed opportunity arrives as a financial record rather than only a pipeline status.
It does. When an opportunity is marked won in Close, Well reads its value and currency and lands it as a transaction against the company it belongs to. Closed sales then sit next to the rest of your finances instead of staying trapped in a pipeline report, so a question about revenue closed this quarter answers from the same place as your bank and billing data.
Every company and person Well builds from Close keeps its Close identifier and a link back to the original. From a workspace page you reach the Close record in one click, and the same identifier travels the other way so you can search from either side. Close stays the system of record for the pipeline; Well holds the financial reading of it beside your other tools.
Well reads leads, contacts, opportunities, and invoices through the Close MCP connection and updates them as they change, with the first connect pulling existing pipeline history in the background. The connection is read-only, so Close remains the place your team works the deals while Well mirrors the closed-revenue side for reporting and agents.
Yes. Disconnecting Close in Well revokes the token and stops further reads right away, and since Well only ever read, there is nothing to roll back on Close's side. The companies, people, and won-deal transactions already brought across stay in your workspace, so historical revenue questions keep answering after the connection is gone.
Pairs well with Close
More in CRM
Popular cross-category
Ready to connect Close?
Connect once. Every lead, contact, won opportunity from Close becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.