What syncs where
A single reference for everything WhenTap reads and writes, and where it goes. Nothing moves that is not listed here.
Webflow
| Direction | What | Detail |
|---|---|---|
| Read | CMS Collections, items and fields | To turn your Collections into bookable staff, services and locations, and to suggest a write-back field mapping |
| Read | Your site list and account email | At install, to know which sites you can connect and who you are |
| Write | A CMS item per booking | Created as a draft in your chosen Collection; updated on reschedule and cancel. See Booking write-back |
| Webhooks | Collection item created / changed / deleted | Registered at install so CMS edits sync within seconds |
WhenTap requests only the Webflow scopes it needs: authorized_user:read, sites:read, cms:read, cms:write, forms:read.
Google Calendar & Outlook
| Direction | What | Detail |
|---|---|---|
| Read | Busy times | Existing events on a connected staff calendar block WhenTap slots |
| Write | An event per booking | Titled "Service — Customer", with the customer's email; moved on reschedule, deleted on cancel |
Connected per staff member. See Connecting Google & Outlook.
Stripe
| Direction | What | Detail |
|---|---|---|
| Write | A Checkout session per paid booking | Created on your connected account, with WhenTap's platform fee set to zero (0%) |
| Write | A refund | Issued on your account when a paid booking is cancelled |
Money pays out to your own Stripe account. WhenTap never stores card details. See Taking payments with Stripe.
| Direction | What | Detail |
|---|---|---|
| Out | Customer confirmation | On booking, with the manage link and add-to-calendar buttons |
| Out | Email reminder | 24 hours before the appointment |
| Out | Owner and staff notification | On each new booking, including intake answers |
The confirmation screen also offers add-to-calendar buttons, so the appointment lands on the customer's own calendar and their device reminds them natively. See Confirmations & reminders.
What stays put
Some things WhenTap deliberately does not move. It never copies your customers' card details (Stripe holds those), and it does not push your WhenTap availability or hours into your Webflow CMS, your hours live in WhenTap, your bookings live in Webflow. If you leave, your bookings are already in your Webflow CMS and your payments in your own Stripe, so nothing has to be migrated back.