Pipedrive

Connect Pipedrive as your CRM and the people you sell to stay in step with the contacts you market to. Persons and leads sync both ways, deals come in as a read-only mirror, your Pipedrive custom fields land on the matching contact fields, and the saved filters you already use in Pipedrive become segments you can target in a campaign.

What it does

Persons sync both ways. A Pipedrive person is a contact here — create or edit one on either side and the change reaches the other.
Leads sync both ways too. A lead has no email or phone of its own in Pipedrive, so we read them from the person it's attached to. That's what lets a lead match an existing contact instead of arriving as a duplicate.
Deals arrive as a read-only mirror. We read them so you can see and target on them; we never create, edit or delete a deal in Pipedrive.
Saved filters become connected segments. Pipedrive has no marketing lists — its saved filters stand in for them, and both people filters and lead filters are supported.
Custom fields map onto contact fields, including number, date, single-select and text fields.
Organisation and owner come in as reference information on the contact — read-only, and never written back.
Changes to a person reach us within seconds. Leads and deals arrive on the regular sync schedule instead.
One CRM at a time. Connecting Pipedrive means disconnecting whatever CRM you have now.

Connecting Pipedrive

There are two ways in, and they end in the same place. Either way you sign in to Pipedrive and approve the access on Pipedrive's own consent screen — there is no API token to generate and nothing to paste, and we never ask for, see or store your Pipedrive password.

From inside the app

Open Settings and go to the Integrations tab.
Choose the CRM category, pick Pipedrive, and click Connect with Pipedrive.
Sign in to Pipedrive in the window that opens and approve the access it lists. It's all or nothing — Pipedrive shows the whole list on one screen and you either approve it or cancel. Cancelling connects nothing and stores nothing; you can start again whenever you're ready.
Pipedrive returns you to a short page confirming the account is linked, and you can close that window. There's nothing to choose here: because you started from inside your own workspace, we already know which workspace the connection belongs to.
Map your Pipedrive fields to your contact fields — see Mapping fields below — and click Confirm mapping & activate.
Sync doesn't start on its own. Optionally narrow what comes in first (see CRM sync scope), then open the connection's details and, under Sync health, click Start sync.

From the Pipedrive Marketplace

Click Install on our listing in the Pipedrive Marketplace. Pipedrive takes you straight to the same consent screen.
Approve the access it lists.
Sign in to the app if you aren't already. This is how we know which workspace the installation belongs to — an install that arrives from the Marketplace carries your Pipedrive company but not your workspace, and we'd rather ask than guess.
Confirm the connection. The confirmation names both the Pipedrive company being connected and the workspace it's being connected to, so you can see exactly what is about to be linked to what — and nothing is written until you confirm. This step exists only on this route: an install that starts in the Marketplace tells us your Pipedrive company but not your workspace, so we ask rather than guess. If it names the wrong workspace, switch workspace and confirm again.
Carry on with field mapping and Start sync, exactly as in steps 5 and 6 above.

Which Pipedrive account the connection uses

The connection acts as the person who authorised it. Whoever clicks through the consent screen is the Pipedrive user the connection behaves as, and that user's own visibility in Pipedrive is the limit of what can sync. Connect as someone with restricted visibility and you get a connection with restricted visibility. Prefer an account that can see everything you want synced, and ideally not one that's about to leave — if their Pipedrive access is removed, the connection stops working. To hand the connection to someone else, disconnect and reconnect as them; there's no way to re-point an existing connection at a different Pipedrive user.

For the full list of what we ask Pipedrive for and why, see CRM permissions reference.

What syncs, and which way

What	Direction
Persons ↔ contacts	Both ways
Leads	Both ways
Deals	In only — a read-only mirror, never written
Organisation and owner on a contact	In only — read-only reference information
Saved filters	In only — they become connected segments

Persons reach us within seconds. Pipedrive tells us when a person changes, and we re-check persons on a slower schedule as well purely to catch anything a dropped notification missed.
Leads and deals arrive on the regular sync schedule. Pipedrive's notifications for those don't carry enough detail to act on safely, so we check for them on a schedule instead. Nothing is missed either way — it just arrives on that schedule rather than immediately.

People and leads

A lead is matched through its linked person. A Pipedrive lead carries no email or phone of its own; those belong to the person it's attached to. We read them from there, so a lead matches an existing contact on email or phone rather than landing as a second copy of someone you already have.
A new lead always comes with a person attached. Pipedrive won't accept a lead that isn't attached to someone. So if you've set the connection to create a Lead when a contact has no match in your CRM, we attach a person too — reusing the Pipedrive person that contact's email or phone already finds, and creating a new person only when nothing matches.
Converting a lead in Pipedrive doesn't deactivate the contact here. Converting is how a lead graduates, not how it goes away: a converted lead is a contact by definition, so the contact stays active and keeps syncing. What does deactivate a contact is the person being deleted in Pipedrive, or the contact being archived here.

Mapping fields

Once you're connected you map your Pipedrive fields to your contact fields. Pipedrive's field list has a few quirks worth knowing before you start:

The standard person fields are all there. First name, last name, email, phone and organisation appear as mapping targets alongside your custom fields.
Number, date, single-select and text custom fields map straight across to a contact field of the matching type.
A Yes/No dropdown can back a true/false field. Pipedrive has no checkbox field, so a two-option dropdown is the usual stand-in. Map one onto a Yes/No contact field and we translate the chosen option for you.
A date and time kept as text syncs correctly. Pipedrive has no date-and-time field either. A timestamp written into a Pipedrive text field maps onto a date-and-time field here, and a timestamp that doesn't say which time zone it's in is read as UTC.
Organisation and owner are reference information, not editable fields. They come in so you can see and target on them — the organisation's name links back to it in Pipedrive — but they're read-only here and never written back.
A new dropdown value is only ever added on our side. When a mapped dropdown gains an option we haven't seen before, we create that option on our own field, never in your Pipedrive field definitions. We don't ask for admin access and nothing we do changes your Pipedrive settings or schema.

If your Pipedrive fields change later, open the connection's details and re-run the mapping step. See Custom fields for what a contact field is and how types work.

Segments from Pipedrive saved filters

A Pipedrive saved filter becomes a connected segment here, so you can target in a campaign the same group you already work with in Pipedrive. Both people filters and lead filters work.

Connected segments carry a provider badge, and a "stale" badge if the connection was removed or the filter no longer exists on the Pipedrive side.
They're managed in Pipedrive, not here. You can view one and target it, but you can't edit its conditions in this app — change the filter in Pipedrive and the change shows up on the next sync.
Every Pipedrive saved filter belongs to one record type. A filter you built while looking at People matches people; one you built in the Leads inbox matches leads. There's no filter that spans both, and that rule carries over here.
If you've limited what syncs in, only the filters you sync are available as segments — see CRM sync scope.

See Segments for how connected segments behave alongside the ones you build yourself.

Limiting what syncs in

You can narrow which Pipedrive people and leads come into the app by picking saved filters as a sync scope. Because filters belong to one record type, pick filters for both people and leads if you want both to keep syncing — a people-only scope means no leads sync in at all. The full picture, including what a scope does and doesn't affect and when you need a force re-sync, is in CRM sync scope.

Disconnecting and uninstalling

Either side can end the connection, and both have the same effect:

Disconnect in the app. In Settings → Integrations, disconnect the CRM. This revokes our access at Pipedrive and uninstalls the app from your Pipedrive account, so there's nothing to tidy up on the Pipedrive side afterwards.
Remove the app in Pipedrive. Uninstalling us from your Pipedrive account ends the connection here too — syncing stops rather than failing quietly in the background.

Either way, contacts already synced into the app stay, with their data intact. Segments built from Pipedrive saved filters stop updating and are marked stale until you reconnect. Reconnecting means going through the consent screen again and redoing the field mapping.

Notes / limits

One CRM connection at a time. To switch providers, disconnect the current one first. This also applies when you're reconnecting Pipedrive a different way — if you connected Pipedrive back when it used an API token, that older connection has to be disconnected before you can connect through the approval window.
Deals are a one-way mirror. We read them; we never create, edit or delete one.
Change notifications cover persons only. Leads and deals arrive on the regular sync schedule.
Nothing we do writes to your Pipedrive settings or schema. We don't ask for admin access, and a new dropdown value is created on our field, not yours.
Pipedrive meters API use against a daily budget. If your account's budget runs out, syncing pauses and the connection reports an error telling you when the budget resets, rather than retrying into an allowance that can't come back until then. It resumes by itself after the reset.
If access is withdrawn, the connection says so. Removing the app in Pipedrive — or changing what it's allowed to do — can invalidate our access straight away, even mid-session. When that happens the connection stops reporting itself as connected: it moves to an error state telling you to reconnect, and syncing pauses until you do. It won't sit there looking healthy while nothing syncs. Reconnecting goes through the usual consent screen; your field mappings and settings are kept.
You're only asked to reconnect when reconnecting is the fix. If syncing stops for a reason that isn't yours — Pipedrive being unreachable, or a fault on our side — the connection shows Sync paused instead of asking you to re-authorize, with a note saying no action is needed. Your connection stays valid, nothing is disconnected, and the label clears by itself as soon as syncing succeeds again. You don't have to do anything, and reconnecting wouldn't help.
Sync errors are kept, not dropped. If a record from Pipedrive fails to save, it's listed on the connection's details so you can fix the underlying problem and retry it — see Integrations and connectors.
Only admins can connect or disconnect a CRM. See Users and permissions.