Pipedrive

Connect FlowBookings to Pipedrive through Zapier and every appointment booked on your Webflow site becomes a person and a deal in your pipeline the moment it lands.

Why connect FlowBookings to Pipedrive

Pipedrive is built around one question: what's moving, and what's stuck? If your bookings never make it in, that picture has a hole in it real, interested people are booking time with you and your pipeline can't see them.

Connect the two together, and every booking enters the pipeline on its own. The booker becomes a person, the booking becomes a deal with its value attached, and your pipeline finally reflects actual demand instead of only the deals someone had time to key in.

Your activity reminders, your forecasts, your win-rate reporting, all of it starts counting the bookings that were invisible before. For a pipeline-driven business, that's the gap between a booking tool and a booking tool that feeds the pipeline you already work.

How it works

A customer books on your Webflow site and FlowBookings records the appointment. Zapier picks it up and creates the matching records in Pipedrive.

Most of the time bookings flow into Pipedrive with new people, new deals. But it can run the other way too: a deal you mark Won in Pipedrive can flip the booking's status back in FlowBookings.

People, organizations and deals

Worth thirty seconds before you build, because Pipedrive models this differently from other CRMs and it shapes every Zap here.

Pipedrive keeps three linked things. A person is the individual who booked. An organization is the company they belong to, if you sell B2B. A deal is the opportunity; the value moving through your pipeline and it attaches to the person and optionally the organization.

A booking gives you what you need for all three: the customer's details make the person, the booking price and service make the deal. Which you create depends on how you sell. Booking individuals, a coach, a clinic, a salon; you likely just need a person and a deal. Selling into companies, add the organization so deals roll up under the right account. This person-plus-deal structure is the bit that makes Pipedrive Pipedrive; keeping the two linked from the first touch is what keeps your pipeline clean.

What you'll need

• A FlowBookings account on any plan
• A free Zapier account (a paid plan comes in for multi-step Zaps like person-plus-deal)
• A Pipedrive account you can connect
• At least one service set up in FlowBookings, and one booking to use as a test

The triggers you're working with

FlowBookings gives Pipedrive two things to react to, plus one action it can receive:

Each record can carry the customer's first and last name, email, the service name, the start and end time, the price, and any custom fields the customer filled in on your form.

Zaps you can build

Create or Update a Pipedrive Person from Every Booking

New Booking → Find or Create Person
A booking comes in, and the booker becomes a person in Pipedrive matched to an existing record if they've dealt with you before, so you don't stack duplicates. Their email, name, and service come across.

Create a Deal for Every Booking

New Booking → Find or Create Person → Create Deal
The one most Pipedrive users actually want. On top of the person, this opens a deal in the pipeline stage you choose, with the booking's price as the deal value and the service in the title, linked to the person. Your pipeline starts filling with real booked demand.

Approve a Booking When Its Deal Is Won

Pipedrive deal marked Won → Update Booking Status → Approved
Move a deal to Won in Pipedrive and the linked booking flips to Approved in FlowBookings, so closing the sale and confirming the appointment happen together.

One rule: once a booking is cancelled, rejected, or already completed, its status is locked so this only acts on bookings still open.

How to set up FlowBookings and Pipedrive integration

Here are the steps to build the integration:

1. Grab your API key

In FlowBookings, go to Dashboard → Integrations → API Key and copy the key. This is what lets Zapier into your account, so treat it like a password — don't paste it anywhere public.

2. Start a new Zap

In Zapier, hit Create → Zaps, search FlowBookings, and pick it as your trigger app.

3. Choose the New Booking trigger

Select New Booking. When Zapier asks you to sign in, paste your API key. It'll pull in a recent booking as sample data so you've got real fields to work with. No bookings yet? Make a quick test one on your Webflow site first, you'll want it for the next step regardless.

4. Add the Pipedrive person

Add an action, choose Pipedrive → Find or Create Person, and connect your Pipedrive account. Find or Create matches on email, so returning customers update their existing person instead of spawning a duplicate. Map customer.email, customer.firstName, and customer.lastName.

5. Add the deal

Add a second Pipedrive action: Create Deal. This is the step that puts the booking in your pipeline:

6. Test it and switch it on

Run the test and check Pipedrive. The person should appear or update, with a deal attached in the right stage. Because this is a multi-step Zap, it runs on a paid Zapier plan. Looks right? Publish.

7. Add the organization (optional, B2B)

Selling to companies? Slot a Find or Create Organization step in before the deal, then set the deal's Organization field to it. Now deals roll up under the right account instead of floating loose.

8. Close the loop from Pipedrive (optional)

To have won deals confirm bookings: build a second Zap triggered on Pipedrive → Deal matching filter (stage = Won), action FlowBookings → Update Booking Status → Approved. You'll need the booking ID stored on the deal to map it back — add it as a custom field in step 5 if you plan to use this.

Here is detailed documentation on how to set up Zapier in FlowBookings.

What you need to know

A few honest edges before you build:

• Use Find or Create, not plain Create. Matched on email, it keeps returning bookers from becoming duplicate people
• The deal Zap needs a paid Zapier plan. Person plus deal is multi-step. A person-only Zap runs on the free tier
• It's fast, not instant. Zapier checks for new bookings every 1–5 minutes on paid plans, up to 15 on the free one
• Reschedules don't update the deal. The trigger fires when a booking is made, not when it changes. A rescheduled booking leaves the person and deal untouched — you'd adjust those in Pipedrive
• Status is one-directional and locked once final. Pipedrive can push a booking to Approved or Completed, but one that's already cancelled, rejected, or completed can't be moved again

Frequently asked questions

Does this cost anything extra?
Zapier integration is available on all FlowBookings plans with no extra charges. You'll need a Zapier account; the free tier covers the basic booking-to-person Zap, and a paid plan comes in once you add deals or organizations.

Will it create duplicate people?
Not if you use Find or Create Person, which matches on email.

Can it create deals, not just people?
Yes, that's the setup above. Map the booking price to the deal value and link it to the person. It's a multi-step Zap on a paid Zapier plan.

Does it handle organizations for B2B?
Yes. Add a Find or Create Organization step and attach the deal to it.

Can Pipedrive update a booking's status?
Yes. A deal marked Won can set the booking to Approved unless it's already cancelled, rejected, or completed, since those are locked.

What happens if a customer reschedules?
The Pipedrive records aren't updated automatically; the trigger only fires on a fresh booking.

Do I need to know how to code?
Not at all. Everything's done by pointing and clicking in Zapier.