When a lead is created in Breakcold
Pulls the new Breakcold lead with its name, company, and email and matches the organization behind it into your Well graph.
Well pulls your Breakcold contact and company records into your workspace to centralize your relationship context
Breakcold feeds person record into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Breakcold’s access.
| From Breakcold | In Well | Relation | |
|---|---|---|---|
| Person record | Contact | Resolves to |
Pulls the new Breakcold lead with its name, company, and email and matches the organization behind it into your Well graph.
Picks up status, tag, or attribute changes on a lead and refreshes the matching company record.
Reads the lead added to a tracked list so the company it represents is brought into your graph for follow-up.
Connect Breakcold over OAuth (MCP DCR): Well registers a client through Breakcold's OAuth Dynamic Client Registration and you approve on Breakcold's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Well brings person record in from Breakcold through live reads, backed by a periodic reconciliation pass. The first sync backfills history in the background and the connection stays live after.
Well resolves each Breakcold entity into contact, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Your data from Breakcold lands in the workspace as contact you can search, chart, and automate.
Ask in plain language. Well answers from your connected Breakcold connection, resolved against the rest of your stack.
Ask anything about your Breakcold connection
Ask about your Breakcold connection…
Well lists Breakcold in the connection check every skill runs before it answers. No skill reads it for a figure yet.
Connects and checks Breakcold
Authorize Well to access your Breakcold account from the connections panel.
Select the specific workspaces or environments where you want your Breakcold company and contact data to appear.
Confirm the connection to start pulling your relationship records into your workspace.
Once connected, your Breakcold data syncs in the background.
Well connects to Breakcold's MCP server via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Breakcold secret. Tokens are scoped to the person record Breakcold exposes and refreshed server-side. Reads only, Well cannot modify or delete Breakcold records.
Read Breakcold records
Resources the Breakcold MCP server exposes, scoped by your OAuth approval.
Resolve person record across your stack
Match identifiers in Breakcold against the same entities your other connected tools expose, so each record carries cross-tool context.
Modify or delete Breakcold records
Not granted; Breakcold is read-only in Well. Write-back is opt-in per connector when a write surface exists.
Store Breakcold passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Well connects to Breakcold to read your company and people records, keeping your workspace updated with your latest relationship data.
No. Well does not sync notes or documents from Breakcold. It only retrieves company and people records.
No. Well has read-only access to your Breakcold data. It does not write, update, or create any records in Breakcold.
Well syncs your Breakcold data in the background to ensure your company and contact records remain current.
More in CRM
Popular cross-category
Connect once. Every person record from Breakcold becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.