HubSpot

Connect FlowBookings to HubSpot through Zapier, and each appointment booked on your Webflow site becomes a contact in your CRM and a deal in your pipeline the moment it comes in.

Why connect FlowBookings to HubSpot

A booking that never reaches your CRM is a customer you're only half tracking. You've got their name and email sitting in your booking dashboard, doing nothing.

Wiring the two together closes that gap on its own. Someone books, and they're in HubSpot: contact created, or matched to one already there, with the service and price attached. Your sequences can fire, your pipeline reflects real demand, and your reporting counts every booking instead of only the ones someone remembered to enter. For a sales-led business, that's the difference between a booking tool and a booking tool that feeds the machine you already run.

How it works

A customer books on your Webflow site and FlowBookings records the appointment. Zapier picks it up and creates or updates the matching record in HubSpot. Set it once, and it runs on its own.

The direction depends on the Zap. Most of the time bookings flow into HubSpot: new contacts, new deals.

Contacts and deals: know the difference first

Worth thirty seconds before you build, because it shapes every Zap on this page.

In HubSpot, a contact is the person. A deal is the potential revenue attached to them. A booking gives you enough to create both: the customer's details make the contact, and the booking's price and service make the deal.

Which you create depends on how you sell. If you just want every booker in your CRM so your marketing and follow-up can reach them, create contacts and stop there. If bookings are the top of a sales pipeline you actively work consultations that turn into contracts, quotes, retainers, create a deal too, so each booking shows up as revenue you're chasing, not just a name on a list.

What you'll need

• A FlowBookings account on any plan
• A free Zapier account (a paid plan comes in for multi-step Zaps like deal creation with a matched contact)
• A HubSpot account you can connect — any tier that Zapier supports, including free HubSpot CRM
• At least one service set up in FlowBookings, and one booking to use as a test

The triggers you're working with

FlowBookings gives HubSpot 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 HubSpot Contact from Every Booking

New Booking → Create or Update Contact · Medium
The core one. A booking comes in and the customer lands in HubSpot — a new contact if they're new, an update to the existing one if they've booked before, so you're not stacking up duplicates. Their email, name, and the service they booked all come across. This is the Zap that makes sure no booker ever slips past your CRM.

Create a Deal for Every Booking

New Booking → Create or Update Contact → Create Deal
For when bookings are the start of a sales conversation. On top of the contact, this drops a deal into the pipeline stage you choose, with the booking's price as the deal amount and the service in the name. Your pipeline starts reflecting real booked demand instead of hand-entered guesses.

Approve a Booking When Its Deal Is Won

HubSpot deal marked Won → Update Booking Status → Approved
The reverse direction. When you move a deal to Won in HubSpot, the linked booking flips to Approved in FlowBookings automatically, so closing the sale and confirming the appointment are one action, not two.

One rule to know: once a booking is cancelled, rejected, or already completed, its status is locked and can't be changed, so this only acts on bookings still open.

How to set up FlowBookings and HubSpot 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 HubSpot

Add an action, choose HubSpot → Create or Update Contact, and connect your HubSpot account when Zapier prompts you.

Pick Create or Update rather than plain Create — it matches on email, so a returning customer updates their existing record instead of spawning a duplicate. This one choice saves you a messy contact list later.

5. Map your booking to the contact

HubSpot field

If you keep a custom property for booking value or source, map price and the service into those too; it makes the contact far more useful inside HubSpot later.

6. Test it and switch it on

Run the test and check HubSpot, and the contact should appear, or update cleanly if they already existed. Looks right? Publish.

7. Add a deal (optional)

Want bookings in your pipeline? Add a third step after the contact: HubSpot → Create Deal. Map price to the deal amount, put the service in the deal name, and pick your starting pipeline stage. Associate it with the contact from step 4 so the deal and person are linked. This makes it a multi-step Zap, which needs a paid Zapier plan.

8. Close the loop from HubSpot (optional)

To have won deals confirm bookings automatically: build a second Zap triggered on HubSpot → Deal in stage Won, with the action FlowBookings → Update Booking Status → Approved. You'll need the booking ID carried on the deal or contact to map it — store it as a property in step 5 or 7 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:

• Match on email, or you'll get duplicates. Always use Create or Update Contact, keyed on email. Plain Create makes a fresh contact every time someone books
• 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 record. The trigger fires when a booking is made, not when it changes. If a customer reschedules, the contact and deal aren't touched — you'd update those in HubSpot yourself
• Deal creation needs a paid Zapier plan. Contact plus deal is a multi-step Zap. The contact-only version runs on Zapier's free tier
• Status is one-directional and locked once final. HubSpot can push a booking to Approved or Completed, but a booking 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-contact Zap, and a paid plan comes in once you add deals or two-way status updates.

Will it create duplicate contacts?
Not if you use Create or Update Contact, which matches on email. That's why we recommend it over plain Create.

Can it create deals, not just contacts?
Yes. Add a Create Deal step and map the booking price to the deal amount. It becomes a multi-step Zap on a paid Zapier plan.

Can HubSpot update a booking's status?
Yes. A deal moving to Won can set the booking to Approved in FlowBookings as long as the booking isn't already cancelled, rejected, or completed, since those states are locked.

What happens if a customer reschedules?
The HubSpot record isn't updated automatically — the trigger only fires on a fresh booking. You'd adjust the contact or deal in HubSpot yourself.

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