The WhenTap blog
Booking on your Webflow site
How to take appointments on your own site, write them back to your own CMS, and keep every booking (and every dollar) yours.
The paid booking that said "pending", a Stripe Connect webhook story
The payment succeeded, the money moved, and the booking still said pending. The cause was a detail of Stripe Connect that is easy to miss: a checkout created on a connected account only notifies the Connect webhook, not your platform one. A build-log on finding it and fixing it for good.
The buffer between appointments, and the bug that let people book into it
Buffer time gives staff a few minutes to breathe between appointments, but only if the schedule actually reserves it. Here is a subtle availability bug we caught in testing, where a booking held its own time but not its buffer, and the one test that surfaced it.
Google and Outlook calendar sync: busy times in, bookings out
Push a booking onto a staff calendar, read their busy times back to block slots. The idea is simple, the failure modes are not. A build-log on how WhenTap works with Google and Outlook in both directions, and the invalid_grant that taught us to surface reconnects.
Your booking widget belongs on your own site, not someone else's
The moment a visitor is ready to book is the moment you least want to send them somewhere else. Why WhenTap embeds the booking flow on your own Webflow site instead of redirecting to a scheduling brand, and what you keep as a result.
Turn your Webflow CMS into a booking engine
Your services and team probably already live in your Webflow CMS. WhenTap treats those Collections as the source of truth for what is bookable, picks up your edits, and can write each booking back as a draft CMS item you own.
Take payment for appointments and keep all of it
A booking that requires payment should still pay you in full. How WhenTap charges through your own Stripe account with no platform cut, holds the slot until the payment clears, and refunds automatically when a paid booking is cancelled.
Getting timezones and daylight saving right in a booking widget
A booking shown an hour off is a missed appointment and a lost customer. How WhenTap stores every time as a single UTC instant, converts per timezone rather than guessing, and stays correct across daylight saving transitions.