Airtable

Airtable is the tool people reach for when a spreadsheet isn't enough but a full CRM is too much. Connect FlowBookings to Airtable through Zapier and every booking on your Webflow site becomes a row in your base the moment it lands. Build the tracker, the lightweight CRM, or the ops database you actually want, and let your bookings fill it in for you.

Why connect FlowBookings to Airtable

Every booking is a record you probably want to keep, sort, and do something with, and track which services sell, see which customers come back, tag jobs by status, and run your own reports. A spreadsheet can do some of that clumsily; a CRM does it rigidly. Airtable sits in the sweet spot: structured like a database, flexible like a spreadsheet, and yours to shape your business works.

Connect your bookings to it, and that database builds itself. Every booking drops in as a row, ready to filter, group, and view exactly how you like. And because Airtable can send changes back to FlowBookings too, it can be more than a record: it can be where you actually manage bookings.

For anyone who likes to run their business their own way, Airtable is the most adaptable home your booking data could have.

The two-way integration

Worth calling out before you build, because Airtable is the one tool here that works in both directions.

Bookings flow out to Airtable. New bookings become rows, and the tracking and lightweight-CRM use most people start with.

Changes flow back from Airtable. Airtable can also trigger an update to your bookings. Fill in a field, submit an Airtable form, move a record, and FlowBookings can update that booking's status in response. That means Airtable isn't just a mirror of your bookings; it can be a place you manage them from.

Most integrations in this set only push data one way. Airtable closes the loop. You can log every booking and run your whole operational workflow from the base, with status changes syncing back to FlowBookings automatically. That symmetry is what makes Airtable worth setting up properly.

Bases, tables, fields and views

Airtable holds data in a base (your database), split into tables (like tabs), made of records (rows) with typed fields (columns — text, date, number, single-select, and more). On top of the same data, you build views: a grid, a Kanban board by status, a calendar, a gallery.

A booking maps onto a record cleanly: one field per piece of booking data. The setup decision is designing your table once: a field for the customer, the service, the date, the price, and a single-select "Status" field you control.

Get those fields right and every booking slots in perfectly, and your views (upcoming this week, grouped by service, by status) all work off the same automatic feed. A little table design up front is what turns a pile of rows into a system.

What you'll need

• A FlowBookings account on any plan
• A free Zapier account
• An Airtable account with a base and table set up to receive bookings
• At least one service set up in FlowBookings, and one booking to use as a test

The triggers and actions you're working with

FlowBookings gives Airtable 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

Log Every Booking to an Airtable Base

New Booking → Create Record
A booking comes in, and a fully-populated row appears in your base: customer, service, date, price. Your tracker or lightweight CRM builds itself, ready to filter, group, and view however you like.

Update a Booking's Status from Airtable

Airtable record updated / form submitted → Update Booking Status
When you change a record in Airtable: approve it, mark it done, submit an intake form against it, FlowBookings updates that booking's status to match.

Run your workflow in Airtable and keep FlowBookings in sync automatically.

Mark Cancellations in Your Base

Booking Cancelled → Update Record
Keep your base accurate when bookings drop. This finds the booking's row and marks it cancelled (rather than leaving it looking active), so your views and reports reflect reality. Needs the booking ID stored on the row to find it.

How to set up FlowBookings and Airtable integration

Here are the steps to build the integration:

1. Design your Airtable table

Before Zapier, set up the table that'll receive bookings. Give it fields for the data you want: Customer Name, Email, Service, Start Date, Price, a single-select Status, and a Booking ID field. That last one lets later Zaps find the right row to update. Match field types to the data (Date for dates, Number for price) so everything lands clean.

2. Grab your FlowBookings API key

In FlowBookings, go to Dashboard → Integrations → API Key and copy the key. Treat it like a password and don't paste it anywhere public.

3. Start a new Zap

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

4. 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 map. No bookings yet? Submit a test one through your Webflow site first.

5. Add Airtable

Add an action, choose Airtable → Create Record, connect your account, and pick your base and table.

6. Map your booking to the record

7. Test it and switch it on

Run the test and check your base, and a new row should appear, fully filled in. Looks right? Publish. Now build the views you want on top: group by service, board by status, whatever fits how you work.

8. Add the two-way status update (optional, the powerful one)

To manage bookings from Airtable: build a second Zap triggered on Airtable → New or Updated Record (say, when you set a record's Status to "Approved"), with the action FlowBookings → Update Booking Status. Map the Booking ID from the row so it updates the right booking.

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

9. Keep cancellations in sync (optional)

Build a Zap triggered on Booking Cancelled, action Airtable → Update Record, matching on the Booking ID field to find the row and set its Status to Cancelled. Your base stays honest.

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

What you need to know

A few honest edges before you build:

• Store the Booking ID. It's the key every "update the right row" and "update the right booking" Zap depends on. Put it on the record in step 6 or the two-way Zaps have nothing to match on
• Design your fields first. Match Airtable field types to the data (Date, Number, single-select). Mapping a date into a text field technically works but breaks your calendar and grouping views
• The status write-back is one-directional and locked once final. Airtable can push a booking to Approved or Completed, but a booking already cancelled, rejected, or completed can't be moved again
• 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 row. The trigger fires when a booking is made, not when it changes and a rescheduled booking won't update its existing row on its own
• Duplicate rows if you're not careful. New Booking always creates a record. If you ever re-run or re-trigger, you can get duplicates — matching on Booking ID (Create-or-Update patterns) avoids it in more advanced setups

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, and the free tier covers the basic log-to-Airtable Zap. The two-way status Zap is more advanced and may need a paid Zapier plan depending on the steps.

Can Airtable update my bookings, or just store them?
Both. Log bookings in as records, and set up the two-way Zap so changing a record's status updates the booking back in FlowBookings. Airtable can be where you manage bookings, not just record them.

Can I build a booking dashboard or CRM in Airtable?
Yes, once bookings flow in as records, build views (grid, Kanban, calendar), group and filter them, and add your own fields. It's a flexible, self-updating booking database.

Why do I need a Booking ID field?
It's how later Zaps find the exact row or booking to update. Without it, a "mark this cancelled" or "sync this status" Zap has no way to match the right record.

What happens if a customer reschedules?
The row isn't updated automatically, and the trigger only fires on a fresh booking. You'd adjust the record yourself.

Do I need to know how to code?
Not at all. A little table design helps, but everything's built by pointing and clicking in Zapier and Airtable.