APIANT.ai / Stories / Wellness spa
Customer story · Wellness spa · Mindbody and Google Calendar
A spa owner wanted Mindbody's bookings and time blocks in Google Calendar, kept in step. Its block sync ran 1,508 times in just over two weeks, all successful.
A wellness spa books its appointments in Mindbody, and the owner blocks out time there too. They connected both apps to APIANT and asked their AI client to build the sync.
Apps in this story
The challenge
Client appointments and the owner's own time blocks were in Mindbody. The owner wanted them in Google Calendar as well, as private busy time that follows every new booking, change and cancellation.
It had to run one way: change nothing in Mindbody, touch only the calendar events it made, and never invite or email anyone.
- 1,508scheduled runs of the block sync, all successful
- Every 15 minthe next 90 days of blocks reconciled into the calendar
- 15calendar changes made on its own: 11 blocks added, 2 moved, 2 removed
- Read-onlyneither sync writes anything to Mindbody
The journey
-
Day 1
The appointment sync
The owner signed up and had the agent build an appointment sync within the hour: each new, changed or cancelled Mindbody booking becomes, moves or leaves a private busy event in Google Calendar. Event titles carry only the client and the service, with no attendees and no email notices. Within a day of signing up, they connected Google Calendar and Mindbody and upgraded from free.
Upgraded from free
-
Day 6
The block sync
Next, the owner's time blocks in Mindbody. The ask covered the awkward cases: recurring blocks, edits, removals, duplicates, and blocks that run past midnight. It passed its test, and about twelve minutes later it was running on its own, every 15 minutes.
Works, every 15 min
-
Day 9
The appointment sync, refined
The owner went back to the appointment sync and had it adjusted. It is still switched on.
-
Days 6 to 22
Running
The block sync has checked the next 90 days 1,508 times, made 15 changes to the calendar on its own (11 blocks added, 2 moved, 2 removed), every run successful. A run takes about two and a half seconds.
What they built
| Sync | What it does | Result |
|---|---|---|
| Appointment sync | New, changed and cancelled Mindbody bookings to private busy events in Google Calendar, titles with client and service only, no attendees or notices | Built Day 1, still switched on |
| Block sync | Every 15 minutes, reconciles the next 90 days of Mindbody blocks into Google Calendar, touching only its own events | 1,508 scheduled runs, all successful; 15 calendar changes |
Both one-way, Mindbody to Google Calendar. Neither writes to Mindbody.
Why it worked
- 01
The edge cases were in the ask.
Recurring blocks, edits, removals, duplicates and blocks past midnight were spelled out before the first build, so the sync handles them by design.
- 02
Tested, then left alone.
The block sync passed its test, went live about twelve minutes later, and ran 1,508 times in just over two weeks, every run successful.
- 03
Careful by default.
Both syncs only read Mindbody, change only the calendar events they made, and never invite or email anyone.
More stories
- A studio owner wanted to see which members were drifting away. He asked his AI client for the Mindbody reports, and had seven working by the next afternoon.
- A yoga studio wanted every Mindbody sale in its membership register, sorted by its own rules. It went live on day three and sorted 21 paid sales by the afternoon of day four.
- A dental practice asked for its online bookings and health forms to land in Cliniko, matched to the right patient or not written at all.
What would you ask for?
Details are taken from the account's own run history and shared without the spa's name.