What exactly triggers the Mindbody integration?
Mindbody appointment attendance after the scheduled end, or a signed-in class booking after the supplied class end.
Mindbody direct integration
Send Google review follow-up after a completed Mindbody visit.
Use Mindbody attendance and schedule data without asking for a review before the visit is actually over. This is a signed provider webhook with explicit setup and testing, not a one-click marketplace install.
Mindbody businesses that want appointment arrivals and class attendance to queue review follow-up only after the scheduled visit has ended.
Exact accepted Mindbody trigger
Mindbody must show that the visit is complete
Appointments require appointmentBooking.updated, Scheduled status, hasArrived=true, and an exact end time. Class roster events require SignedIn; delivery waits until the supplied class end or, when only a start is available, a conservative four-hour buffer.
Mindbody direct uses a private signed webhook and the customer details included in eligible booking or roster events. It is not a Mindbody password handoff. Someone with webhook permissions must create the subscriptions and copy the signing key into ReviewsRelay.
Required customer handoff
- A stable booking or roster event ID
- An arrived appointment or signed-in class status
- A customer record with name and email
- A scheduled appointment or class end time
Automatically ignored
- Canceled, no-show, or non-attended visits
- Arrivals before the scheduled appointment end
- Duplicate event IDs
- Customers without a usable email address
- Opted-out contacts or customers contacted within 90 days
Provider-specific setup
Connect Mindbody, prove one event, then enable live intake
- Create the Mindbody direct connection
Save the private webhook signing key in ReviewsRelay and copy the generated destination URL.
- Subscribe to the right visit events
Use appointmentBooking.updated for appointments and classRosterBookingStatus.updated for classes. classRosterBooking.created is also accepted when the booking is already SignedIn.
- Run an appointment or class test
For an appointment, send Scheduled + arrived with an end time. For a class, send SignedIn with a class end or start time. Use contact details you control.
- Confirm the not-before time
The accepted event should show a request hold until the visit ends. Confirm a missing appointment end, no-show, cancellation, or unsigned delivery is rejected.
Go-live checks
Confirm the provider evidence, customer data, and duplicate behavior
- The event is an accepted appointment or class roster event
- The attendee is Arrived or SignedIn under the exact provider rule
- A valid name, email, and stable booking identity are present
- The request cannot move before the calculated visit end
- Repeating the same booking event does not create a second queue item
Operational controls
- Signed webhook verification is required
- Arrived appointments wait until their exact scheduled end
- Signed-in classes use the supplied class end or a conservative four-hour buffer when only a start time is provided
- The connection can be tested, paused, rotated, or disconnected in ReviewsRelay
Mindbody Webhooks documentation is the official provider source for the webhook contract.
- Compare all connection pathsDirect providers, Zapier, Make, secure webhooks, CSV, and manual entry
- Preview the downstream workflowSee what happens after an eligible customer reaches ReviewsRelay
Practical outcomes
- Separate appointment and class rules
- Wait until the scheduled visit ends
- Keep cancellations and no-shows out
- Inspect the calculated request hold
Workflow
- Create the Mindbody direct connection
- Subscribe to the right visit events
- Run an appointment or class test
- Confirm the not-before time
Safety guardrails
- Signed webhook verification before payload processing
- Canceled, no-show, or non-attended visits
- Arrivals before the scheduled appointment end
- Duplicate event IDs
- Customers without a usable email address
Frequently asked questions
What customer data does ReviewsRelay need from Mindbody?
A stable booking or roster event ID. An arrived appointment or signed-in class status. A customer record with name and email. A scheduled appointment or class end time.
Which Mindbody events are ignored?
Canceled, no-show, or non-attended visits. Arrivals before the scheduled appointment end. Duplicate event IDs. Customers without a usable email address. Opted-out contacts or customers contacted within 90 days.
Is the Mindbody connection a one-click install?
Mindbody direct uses a private signed webhook and the customer details included in eligible booking or roster events. It is not a Mindbody password handoff. Someone with webhook permissions must create the subscriptions and copy the signing key into ReviewsRelay.
Can I test the Mindbody connection before enabling it?
Yes. Use contact details you control and verify these checks: The event is an accepted appointment or class roster event; The attendee is Arrived or SignedIn under the exact provider rule; A valid name, email, and stable booking identity are present; The request cannot move before the calculated visit end; Repeating the same booking event does not create a second queue item.
Does ReviewsRelay need my Mindbody password?
No. ReviewsRelay never asks for your Mindbody sign-in password. The direct connection uses a private signed webhook and the minimum configured credentials needed for customer lookup.
Related review automation pages
- IntegrationsReview request automation
- SquareSquare Google review request automation
- VagaroVagaro Google review request automation
- SafetySafe Google review automation
- Free toolsFree Google review tools
- Profile auditGoogle Business Profile audit tool