Pipedrive

Connect Pipedrive and Preb keeps your CRM in sync with every booking automatically. Leads, booked calls, reschedules, cancellations, no-shows, and call outcomes all flow into Pipedrive as persons, activities, notes, and pipeline deals — and changes you make in Pipedrive flow back to Preb, so the two stay in agreement without anyone copying data by hand.

It's a two-way, native integration: no Zapier, no CSV exports. Preb becomes the scheduling engine in front of your Pipedrive pipeline, and — because Preb is where your ad-click IDs live — a deal you mark won anywhere fires the Purchase conversion back to your ad platforms, closing the attribution loop.

Adding the app

Prerequisites

• A Pipedrive account where you can install apps.
• A Preb workspace where you are an admin — connecting and configuring Pipedrive is an admin-only action.

Connect your Pipedrive account

Set up what syncs

After connecting, open Integrations → Pipedrive to configure the sync. Each card is optional — turn on only what you need:

You can also override any of these per event type from the Pipedrive tab in the event-type editor (it appears once a connection is active).

Troubleshooting

Still stuck? See our contact & support guide and we'll help you sort it out.

Using the app

Once Pipedrive is connected, these features work automatically based on what you enabled. Each one lists what it does and what needs to be in place first.

Leads and persons sync as they come in

• Use case: A visitor completes the first step of your booking form. Preb upserts them as a Pipedrive person (matched by email), sets your mapped label for that moment, assigns the owner, and fills any mapped fields — including UTM parameters and ad-click IDs.
• Prerequisites: Contact sync is on. Unmapped labels are left untouched, so your existing Pipedrive data is safe.
• Optional — unfinished leads too: Workspace owners can additionally turn on Send unfinished leads to your connected CRM (Settings → Data retention). Visitors who started typing into the form but never submitted are then pushed to Pipedrive about two hours later. Leads synced this way are kept (they're in your pipeline now) instead of being auto-deleted after 30 days — and they're your responsibility under privacy law like any other CRM contact.

Bookings become activities on the timeline

• Use case: A call is booked. Preb logs an activity on the person's Pipedrive timeline with the time, duration, the meeting link, and the booking-form answers. Reschedules update the same activity in place; cancellations and no-shows mark it done with a [Canceled] / [No-show] marker; a recorded call outcome marks it done. The activity is never deleted, so the history stays on the timeline.
• Prerequisites: none — activities sync whenever contact sync is on.

The pipeline follows the call

• Use case: As a lead moves from booked to showed to won, Preb moves a single deal through your pipeline stages and records the deal value on a sale. There's always one active deal per contact per pipeline — no duplicates — and a closed deal is history: when a customer whose deal is already won or lost books again, Preb starts a fresh deal for the new sales cycle instead of reopening the old one, so your revenue reporting stays accurate. Different no-sale reasons (follow-up, unqualified, not interested) can land on different stages.
• Prerequisites: A pipeline is selected. A sale marks the deal won and a disqualification marks it lost by status, whether or not you mapped a stage for those moments.

Two-way sync keeps both sides honest

• Use case: Someone edits a synced person in Pipedrive — name, phone, email, or owner — and Preb picks it up and updates its own records, without echoing the change back and causing a loop.
• Prerequisites: The persons sync-back toggle is on. A person's ad-attribution data is never overwritten by a sync-back.

Won in Pipedrive fires your ad conversion

• Use case: You mark a Preb-created deal won in Pipedrive. Preb records the sale and fires the Purchase conversion to your connected ad platforms — using the ad-click IDs it captured at booking time — so revenue is attributed even when the deal closes in the CRM. It fires exactly once, whether you close the deal in Pipedrive or in Preb.
• Prerequisites: Deal sync-back is on, and you've connected an ad platform (e.g. Meta) in Preb's tracking settings.

Owner-based routing

• Use case: A returning lead who already has a person owner in Pipedrive books again. Preb offers only that owner's availability, so the relationship stays with the person who owns it. If the owner isn't available or isn't mapped, Preb falls back to normal round-robin. Bookers on personal email domains (gmail, outlook, …) skip owner routing by default, so a stale CRM record never pins a new person to the wrong host.
• Prerequisites: Owner routing is enabled on a round-robin event type, and the host is linked to their Pipedrive user.

Permissions Preb requests (and why)

When you connect, Pipedrive asks you to authorize a set of scopes. Preb requests only what the features above need — nothing is used for advertising, resale, or profiling, and Preb never reads data it doesn't act on.

Data & privacy

• What Preb stores: the connection's encrypted access/refresh tokens, the Pipedrive account id, a per-connection secret used to authenticate inbound webhooks, and the mapping choices you configure (which pipeline, labels, fields, and team members to use). It does not copy your Pipedrive person database into Preb.
• Direction of data: Preb writes booking and outcome data into Pipedrive, and reads back only the specific changes it needs to stay in sync (a person edit, a deal status change). A person's ad-attribution data is never overwritten by a sync-back.
• Removing your data: disconnecting from Preb, or uninstalling the app in Pipedrive, stops all syncing. Records already written to your Pipedrive account are yours and are left in place. A person deleted in Pipedrive is unlinked on Preb's side immediately.

Removing the app

You can disconnect from either side.

From Preb

Go to Integrations → Pipedrive and click Disconnect. Preb removes its back-sync webhooks and stops syncing immediately.

From Pipedrive

Uninstall the Preb app under Settings → Marketplace apps in Pipedrive. This revokes Preb's access; Preb detects it, marks the connection as needing a reconnect, and emails your workspace admins.

What removing the app does

• Preb stops creating and updating Pipedrive persons, activities, and deals for future bookings, and stops accepting changes from Pipedrive.
• Persons, activities, and deals already in Pipedrive stay there — disconnecting doesn't delete anything in your CRM.
• Your Preb-side settings (labels, field mappings, pipeline and owner mappings) are kept, so reconnecting the same account picks up exactly where you left off.

Known limitations

• Activities and deals edited in Pipedrive: a person edit or a deal status change syncs back to Preb, but moving an activity's time inside Pipedrive won't change the Preb booking. Reschedule and cancel from Preb (or the invitee links) — those update Pipedrive automatically.
• Person labels are opt-in. Pipedrive labels are account-specific, so Preb only sets a label for a moment when you've mapped one.