Turn your Webflow CMS Collections into a booking system

Here is the idea no other scheduling tool is built around: the things people book from you are already in your Webflow CMS. Your team is a Collection. Your services are a Collection. Your locations are a Collection. So why retype them into a second system? This is how booking against the CMS actually works.

The double-entry problem

Bolt-on schedulers force you to maintain two copies of reality. You add "Dr. Avery Stone" and "45-minute consultation" to Webflow for your website, then add them again to Calendly or Acuity for booking. Change a price? Update it twice. Add a therapist? Add them twice. The two systems drift, and your site ends up advertising a service your booking tool has never heard of.

Map once, sync both ways

The fix is to make the CMS the single source of truth. You point WhenTap at a Collection, map its fields once, and it keeps itself in sync:

• A Team Collection → bookable staff, each with their own hours and calendar.
• A Services Collection → bookable services, with duration, price and buffer read from your fields.
• A Locations Collection → for multi-location businesses.

Edit a service in Webflow and the booking widget updates. Add a Collection item and it becomes bookable. The field mapping is auto-detected — "Duration" maps to duration, "Price" to price — so the whole thing takes a minute.

Real-time via webhooks

Syncing isn't a nightly batch. WhenTap registers Webflow webhooks, so the moment a Collection item is created, changed or deleted, the bookable resource updates within seconds. Change a price at 2pm and the 2:01pm visitor sees it.

Closing the loop: bookings as CMS items

The wedge runs both directions. Turn on write-back and every confirmed booking is created as a native item in a Bookings Collection: customer, service, staff, date. Now your bookings are Webflow data. You can:

• Render an "upcoming events" list on your site straight from the CMS.
• Build a client dashboard with Webflow's own tools.
• Trigger automations in Make or Zapier off the CMS item.
• Export your entire history because it's yours, not locked in a SaaS.

What stays in WhenTap

The CMS owns the what (services, staff, the booking record). WhenTap owns the scheduling logic: availability rules, buffers, timezone math, calendar sync, reminders, payments. CMS is the source of truth; WhenTap extends it with the things a CMS was never meant to do. Clean division, no drift.