Calendar mapping & sync
A calendar mapping tells AutoSync "this Mindbody appointment type or class program maps to that HighLevel calendar." Bookings for a mapped type sync both directions; bookings for an unmapped type are simply skipped — not an error.
Which calendar type to use
The right HighLevel calendar depends on whether the booking needs to be assigned to a specific team member.
| You need… | Use |
|---|---|
| A class where it doesn't matter who runs it | Event Calendar — group booking, no per-person staff |
| Appointments assigned to one staff member | Service Calendar with a single mapped staff member |
| Appointments that any of several staff could run | Service Calendar with multi-staff mapping to real HighLevel users |
Note that classes always use Event Calendars — only appointments use Service Calendars, where the mapped staff (one or several) drive HighLevel's availability and assignment.
Sync mode & booking priority
- 2-way (default) — bookings flow both directions.
- 1-way — the platform is always the source of truth; HighLevel changes are ignored.
- None — no automatic calendar sync (workflow actions can still book manually).
In 2-way mode, booking priority (Platform / CRM / Neutral) decides who wins a conflict. The Sync Booking workflow action always books regardless of the sync-mode setting.
Reschedules & cancellations sync too
In 2-way mode, edits made in HighLevel reach the platform: rescheduling an appointment in HighLevel moves the same booking on the platform (its payment and attached order stay put), and cancelling in HighLevel cancels it on the platform. If a move cannot be completed automatically, AutoSync raises an alert naming the client, the service, and the old and new times — so your team can fix it in seconds instead of discovering it at the door.
Map a whole program (classes)
Instead of listing every class description, you can map by program. New class descriptions in that program are captured automatically — useful for studios like F45 that rotate class names.
Auto-pause
AutoSync pauses a mapping (and tells you why) when the mapped appointment type or class is deactivated on the platform, the HighLevel calendar is deleted or disabled, or your Mindbody Site ID changes. Paused mappings don't sync — the Calendar Sync page shows the reason and lets you re-map.
Out-of-service chairs
If the booking platform declines bookings into a room or chair that its own schedule shows as free (usually because staff have blocked the chair out of service), AutoSync temporarily stops offering that chair in HighLevel and sends a Chair Out of Service alert. The chair returns automatically as soon as any platform booking lands in it — or after 7 days. Fewer offered slots always beats a double-booked chair.
Fixing "the slot you selected is no longer available"
This is the most common booking error, and it almost always means your HighLevel calendar availability doesn't match what's actually available on the booking platform. Check that the HighLevel calendar's duration, appointments-per-slot (capacity), and days/times match your platform. If most bookings happen on the platform, set wider HighLevel availability; if you also let people book through HighLevel, the availability must line up exactly to avoid the error.
Seeing repeated failures? Open the Activity Log, filter Booking Activity to Failed, and look at the Error Response column — it names the exact cause per booking.
Last updated August 2026