Mindbody Zoom Integration for Virtual Classes

Does Mindbody integrate with Zoom?

Yes, in two ways. Mindbody has its own virtual and livestream class options, and at the time of writing those can work with Zoom. Separately, a sync can use Mindbody’s public API (classes, class schedules, clients and visits) and Zoom’s API (creating meetings and adding registrants) to handle the handoffs that the built-in route leaves to manual work. Confirm the current setup and plan requirements in Mindbody’s help documentation, because both features and plan rules can change.

If you run a few virtual classes a week, with one teacher per class and the same clients turning up, the built-in route can be enough. The trouble starts when bookings change after the link has gone out.

How do you set up Zoom for Mindbody classes the manual way?

The manual pattern has three parts:

1. Schedule the class in Mindbody as a regular class on your class schedule, with the online version clearly named.
2. Create the Zoom meeting in Zoom, either by hand or by reusing a recurring meeting. Note the host account you used.
3. Put the link where booked clients will see it: the class description, the confirmation email, or a manual message sent before class.

To check the process, use the class roster in Mindbody and your Zoom scheduled meetings list. Then place a test booking for a staff member or friendly client. Note what they receive and when. If the link only appears in the class description, a client who books late may never see it.

Booker businesses usually do the same thing: paste the link into the appointment or service notes, or send it by hand. The same limits apply.

Where does the manual way break?

The built-in or manual route fails in predictable places. Most of them show up only after a class has started.

Situation	Manual / built-in	With a sync (Pandaflow)
New virtual class on the schedule	Create the Zoom meeting by hand or reuse a recurring one	A meeting is created for each class occurrence
Client books	Link sits in the description or a general email	Client gets their own join link after booking
Client cancels	Link still works for anyone who has it	Registration is removed from the meeting
Waitlist client moves in	Staff must remember to send the link	Link is sent when the client is promoted
Hybrid capacity	One capacity number per class in Mindbody; needs a separate virtual class or a manual rule	The virtual class roster drives the Zoom registrants
Attendance	Compare Mindbody attendance with the Zoom participant report by hand	Joins can be compared with bookings; you still decide how attendance is recorded
Replay	Upload and send by hand	Recording link goes to the class’s booked clients once it is ready

A few specific failure points:

• Reused links leak. Anyone who ever received the Monday 9:00 link can join next Monday. A new meeting per occurrence, or a unique link per registrant, stops a link being useful once the class is over.
• The roster is only final at start time. Late bookings, late cancels and same-day waitlist moves all change who should have a link. A link sent once at booking time misses them.
• Hybrid capacity creates friction. Mindbody tracks one booking list and one capacity number per class. A hybrid session with both in-room mats and virtual spots needs a clear rule, such as listing the virtual session as its own class on the schedule, so the roster feeding Zoom stays distinct.
• Attendance does not match. Mindbody attendance reflects what staff marked at check-in. Zoom’s participant report reflects who joined. They rarely agree, so teachers reconcile by hand if no-shows or class-pass deductions matter to them.
• One host can’t run two meetings. A single Zoom host account generally cannot run overlapping meetings. Back-to-back classes with a short overlap, or two teachers sharing a login, cause collisions.
• Time zones confuse people. Mindbody shows times in your location’s time zone. An online client may be elsewhere. Reminder emails should clearly state the time zone.

How does a Mindbody-to-Zoom sync create meetings from the schedule?

The outcome you want is simple: each virtual class on the Mindbody schedule gets its own Zoom meeting for that occurrence, with the class name and time, under the right host.

Before you start, decide how virtual classes are identified (a class name, a class type, or a naming pattern) and which Zoom host account runs each one. Those two decisions go into your description.

With Pandaflow, the setup is:

1. Start free. Create an account and check the Mindbody integration details for how Mindbody connects.
2. Connect your apps. Connect Mindbody and Zoom.
3. Describe what you want in plain English. For example: ‘For every class named Live Stream Pilates on the Mindbody schedule, create a Zoom meeting for that class time, hosted by the studio’s shared account, and send each booked client their own join link by email.’
4. Review a few records. Check the meeting created for one upcoming class and the registrants on it.
5. Go live.

Pandaflow’s AI sets up the sync and keeps it running, repairing it when something changes. There are no workflows, templates or settings for you to configure. You can deploy in our cloud or yours. If you want to check tiers before starting, see pricing (Lite $79, Silver $299, Gold $499 a month).

Once it runs, you should see a meeting for each occurrence of the virtual class, booked clients registered on it, and, if you turn it on, a Slack alert when something fails, such as a class with no host assigned.

How do you send links only to booked clients, and stop sharing?

Zoom registration is the mechanism. Each registrant receives a unique join link via Zoom’s registration API. A sync adds a client when they book and removes them when they cancel. A cancelled client’s old link stops working for them.

Two extra layers help, but neither is an absolute barrier. A waiting room lets you admit people one at a time. A passcode keeps out people who only have the meeting ID. A client can still share their own screen or invite someone into the physical room, so treat these controls as friction rather than an ironclad lock.

For delivery, the sync uses the client’s contact details from Mindbody and sends the link by email or text through Twilio. If your messages already run through HubSpot, Klaviyo or Mailchimp, the link can go through those instead.

Timing matters:

• The link is sent at booking.
• A reminder goes out shortly before class.
• The roster is checked again up to the start time, so late bookings get a link.
• A waitlist client who moves into the class gets their link at that point.

To test it, place a test booking, confirm the link arrives, cancel the booking, and confirm the link no longer gets the test client into the meeting.

What about recordings and replays?

Decide whether to record before you decide how replays go out. A recording usually shows other clients’ faces and names. Get consent and decide who can watch.

Cloud recording needs a paid Zoom plan at the time of writing, and the file is processed after the meeting ends, not instantly. Send replay links after processing is done, not in the reminder email.

Sending the replay only to clients who were booked (or only those who attended) is safer than posting a public link. Pandaflow can be set up to pick up a finished recording and send it to that class’s booked clients if your description asks for it.

Whether a replay counts against a class pass is a studio policy question. Neither Zoom nor the sync decides it.

What can go wrong?

• No host is assigned to a class, so no meeting is created.
• Two classes overlap on one host login.
• A client’s email is missing or different in Mindbody, so the link goes to the wrong place or nowhere.
• The link email lands in spam. Ask clients to add your sender address.
• Time zone confusion in reminders.
• Expiring or passcode-protected replay links that clients cannot open later.

For related how-tos, browse more guides.