What syncs where
A single reference for what WhenTap reads and writes, and where it goes.
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 authorization, when the site list opens, and once a day to check WhenTap can still reach each site |
| Write | Site webhooks | Registered on each connected site so CMS edits reach WhenTap; removed when you pause or remove the site or delete the account, and while the account has no active plan. A removal Webflow does not accept is retried for up to 7 days |
| Write | WhenTap's booking script | Registered with Webflow and added to the site footer when you click Add to site on the Embed page; removed when you click Remove from site, remove the site, or delete the account, from every site WhenTap can still reach (publish to make it live). Uninstalling WhenTap removes it too |
| Read | The scripts WhenTap added | To show on the Embed page whether the booking script is on the site |
| 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 when you connect a site, so WhenTap re-reads a mapped Collection a few seconds after an edit |
WhenTap reads and writes the primary locale of your site only; secondary locales are not read or written.
WhenTap requests only the Webflow scopes it needs: authorized_user:read, sites:read, sites:write (only to register those webhooks), cms:read, cms:write, custom_code:read and custom_code:write (only for its own booking script).
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 |
|---|---|---|
| Connect | Your Stripe account | Linked when you click Connect Stripe; access is revoked when you disconnect |
| Write | A Checkout session per paid booking | Created on your connected account, with no WhenTap application fee (0%) |
| Write | A refund | Issued on your account when a paid booking is cancelled |
| Read | Payment status | To confirm a paid booking if a Stripe notification was missed |
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 an add-to-Google-Calendar button |
| Out | Email reminder | 24 hours before the appointment, when booked more than 24 hours ahead |
| Out | Change and cancel emails | To the customer when a booking moves or is cancelled, with the refund outcome |
| Out | Owner and staff notification | On each new booking (with intake answers), on customer changes and cancels, and on a failed refund |
| Out | Account emails | Sign-in links, team invitations, plan confirmations, and a notice when WhenTap loses access to your Webflow account |
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 with write-back on, your bookings are already in your Webflow CMS and your payments in your own Stripe, so nothing has to be migrated back. See Uninstalling WhenTap for what stays in your Webflow site and how to remove it.