When a Pipedrive deal is updated
Picks up stage or owner changes on a deal and refreshes the linked company record.
Bring your Pipedrive company and contact records into Well to map your customer relationships
Pipedrive 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 Pipedrive’s access.
| From Pipedrive | In Well | Relation | |
|---|---|---|---|
| Company record | Customer | Enriches | |
| Person record | Contact | Resolves to |
Picks up stage or owner changes on a deal and refreshes the linked company record.
Captures the new lead and matches the organization behind it into your company graph.
Reads the person's name, email, and phone and links them to the parent organization in Well.
Detects edits to an organization's name, address, or custom fields and refreshes the matching Well company.
Connect Pipedrive over OAuth (MCP DCR): Well registers a client through Pipedrive's OAuth Dynamic Client Registration and you approve on Pipedrive'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 Pipedrive 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 Pipedrive 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 Pipedrive lands in the workspace as customer, and contact you can search, chart, and automate.
Ask in plain language. Well answers from your connected Pipedrive connection, resolved against the rest of your stack.
Ask anything about your Pipedrive connection
Ask about your Pipedrive connection…
Authorize Well to access your Pipedrive account through the secure connection screen.
Select the specific organization or workspace you want to sync with Well.
Confirm the connection to start pulling your company and people records into your workspace.
Once connected, Well syncs your CRM directory in the background.
Well connects to Pipedrive'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 Pipedrive secret. Tokens are scoped to the company record, and person record Pipedrive exposes and refreshed server-side. Reads only, Well cannot modify or delete Pipedrive records.
Read Pipedrive records
Resources the Pipedrive MCP server exposes, scoped by your OAuth approval.
Resolve company record, and person record across your stack
Match identifiers in Pipedrive against the same entities your other connected tools expose, so each record carries cross-tool context.
Modify or delete Pipedrive records
Not granted; Pipedrive is read-only in Well. Write-back is opt-in per connector when a write surface exists.
Store Pipedrive passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Well reads company and people records from your CRM. It does not pull deal files, documents, or deal revenue transactions.
No. Well only reads data from Pipedrive to build your context layer. It does not write, update, or sync any records back to your Pipedrive account.
Well syncs with Pipedrive in the background to ensure your company and people directory reflects recent updates made in your CRM.
More in CRM
Popular cross-category
Connect once. Every company record, person record from Pipedrive becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.