ReviewsRelay Start free

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.

Start freeSee it work

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

  1. Create your private link

    Create an inactive ReviewsRelay link first. No keys are needed and customer intake stays paused.

  2. Register the webhook in your provider

    Paste the private ReviewsRelay Mindbody URL into the Mindbody webhook subscription. Subscribe to appointmentBooking.updated, classRosterBookingStatus.updated, and client.updated for later email opt-outs. You may also subscribe to classRosterBooking.created for customers already marked SignedIn. Keep native webhook payloads unchanged so signatures can be verified.

  3. Save the required credentials

    Copy the message signature key from your Mindbody subscription and save it in ReviewsRelay. Keep client.updated subscribed for later email opt-outs.

  4. Verify a completed event while paused

    Send a completed event using your own contact and customer record, then select Check test. Confirm the earliest send time before enabling intake. ReviewsRelay verifies the signature, customer lookup and eligibility without creating a request or contacting anyone.

  5. Enable customer intake

    After the test passes, enable intake explicitly. New eligible events enter the queue; sending follows your request settings. Keep cancellations and opt-out events subscribed when intake is paused.

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.

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 your private link
  • Register the webhook in your provider
  • Save the required credentials
  • Verify a completed event while paused
  • Enable customer intake

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 exactly triggers the Mindbody integration?

Mindbody appointment attendance after the scheduled end, or a signed-in class booking after the supplied class end.

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