How to set up Pipedrive
To connect Pipedrive, you’ll need your company domain and an API token.Connection details
Once the connector is created, you can:
- Set up a Pipedrive data model — Create data models from your Pipedrive objects to trigger Plays and power model search actions.
- Use Pipedrive in workflows — Choose Pipedrive from the node catalog within a Play, Tool, or Agent.
Pipedrive actions
Get record
Retrieve a single record from Pipedrive by its ID. Use cases- Data lookup – Fetch record details for use in workflows
- Conditional logic – Retrieve data to make routing decisions
- Enrichment context – Get existing data before updating
Insert record
Create a new record in Pipedrive. Use cases- Lead capture – Create new leads from inbound sources
- Organization creation – Add new companies to your pipeline
- Deal creation – Create deals for new opportunities
Update records
Update existing records that match specified criteria. Use cases- Data enrichment – Update records with enriched information
- Status updates – Update deal stages or lead statuses
- Field updates – Bulk update specific fields
Use the Skip if exist option to preserve existing data and only fill in
missing fields.
Upsert records
Insert new records or update existing ones based on matching criteria. Use cases- Data sync – Sync records from external systems without duplicates
- Idempotent operations – Safely retry operations
- Master data management – Maintain a single source of truth
Update records and Upsert records match only on the selected Field from Pipedrive: a record whose value appears in another field (a note, a different custom field) is not a match, and the comparison is case-insensitive. The matching field itself is not rewritten on update unless you map it. When Upsert records creates a record, it sets the matching value on it (name, title, email, phone, address, or a custom field) so the next run finds it.
Field from Pipedrive offers the record ID, any custom field, and the fields Pipedrive can search for that object type: name, address and notes for organizations, name, email, phone and notes for persons, and title and notes for deals and leads. A lead shows the email, phone and names of the person and organization it is linked to, but Pipedrive does not search leads by them, so matching a lead on one of those is not offered and stops with an error if an older node is still set to it — match the lead on its title, notes, a custom field, or its ID instead.
Both actions update every matching record by default. Turn on Fail on multiple matches to leave ambiguous matches, such as two organizations named “Acme”, untouched: the action writes nothing and stops with an error naming the number of records that matched.
Delete records
Delete records from Pipedrive that match specified criteria. Use cases- Data cleanup – Remove outdated or invalid records
- GDPR compliance – Delete personal data upon request
- Pipeline hygiene – Remove unqualified leads
Delete records matches only on the selected Field from Pipedrive, like Update records: a record that mentions the value in another field (a note, a different custom field) is not deleted. Every matching record is deleted by default; turn on Fail on multiple matches to leave ambiguous matches untouched, in which case the action deletes nothing and stops with an error naming the number of records that matched.
Search records
Retrieve multiple records from Pipedrive based on search criteria. Use cases- Data retrieval – Find records matching specific terms
- Duplicate detection – Search for existing records before creating new ones
- Bulk operations – Retrieve records for processing in group nodes
Pipedrive data models
Cargo allows you to create data models on top of your Pipedrive data that can be used to trigger Plays and power workflows.Creating Pipedrive data models
Configure the following when creating a data model:Object types available
Organization models
Organization models
Use cases - Track company records with custom fields - Trigger workflows
when organizations are created or updated - Build account-based workflows
Person models
Person models
Use cases - Manage contact information and relationships - Trigger
workflows on contact changes - Power contact enrichment workflows
Deal models
Deal models
Use cases - Track opportunities through your pipeline - Trigger
workflows on deal stage changes - Monitor deal velocity and conversion
Lead models
Lead models
Use cases - Manage early-stage prospects - Trigger qualification
workflows - Track lead conversion rates

