Mindbody
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | Clinics and wellness | Enter your Mindbody account details in bubbl3 |
Mindbody isn't offered yet. This page says what it will do and what you can use meanwhile: a Lead URL, or Zapier, Make or n8n.
What it does
Mindbody runs fitness studios, gyms, spas and wellness businesses. Connecting a site sends each new client, appointment booking and class booking to bubbl3 as it's made. Each one:
- becomes (or updates) a contact, matched on phone and email, keeping only the minimum client details (see below);
- goes through the connection's lead source, which sets its labels, owner, consent and workflow;
- for a client bubbl3 already has, a booking also counts as the conversion event Appointment booked.
A client whose account texts are off in Mindbody (on a new client, a booking or an update) is opted out in bubbl3 and never texted. That opt-out stays in bubbl3: it isn't copied to your other connected CRMs. bubbl3 never books, sells or messages anything in Mindbody.
Setup
- In Mindbody, activate bubbl3 for your site.
- In bubbl3, open Settings, Integrations, choose Mindbody and enter your site ID and a staff login for the site. bubbl3 reads the site, then asks Mindbody to check the staff login once: only your site's own staff can pass, which shows the site is yours. bubbl3 doesn't keep the login.
- Set the lead source's consent and workflow. Mindbody's account-texts setting is used as consent where it's sent.
| What you enter | Where to find it |
|---|---|
| Site ID | In Mindbody, Settings, Business information. Activate bubbl3 for the site first |
| Mindbody staff username | The site owner's or a staff member's Mindbody login |
| Mindbody staff password | Used once for that check, never stored |
To protect your site, bubbl3 stops checking staff logins for a site after 5 failed tries in an hour, whichever bubbl3 workspace they come from. Try again after the hour.
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: new clients and bookings for this workspace, and the lead source is paused.
- Deleted at once: the connection's stored credentials. Your staff password was never kept.
- Kept: contacts made from Mindbody, with their messages, labels and consent, and only the minimum details. The paused lead source stays. The connection's account details (the site ID) stay on the disconnected connection.
- Deleted later: stored deliveries are deleted 30 days after they arrived.
To stop Mindbody sending bubbl3 anything for the site, deactivate bubbl3 for it in Mindbody too.
Data shared
From Mindbody to bubbl3: new clients and bookings for your site. bubbl3 keeps only first and last name, mobile (else home) phone, email, the account-texts setting as consent, and the booking's start time.
From bubbl3 to Mindbody: nothing. The staff login is sent to Mindbody once, to check it, and never stored.
Patient data
Mindbody can hold patient health information, so bubbl3 keeps only the minimum from its records: name, phone, email, consent and appointment time. Every other field, such as notes, dates of birth, insurance or health details, is dropped before anything is saved, and message templates can't use clinical fields.
Need another field? It takes bubbl3's HIPAA add-on and a signed business associate agreement. Contact bubbl3 support: bubbl3's staff add the field to your connection, the addition is recorded in your audit log, and the field is kept on the contact where message templates can't use it.
Scopes and permissions
Mindbody has no scopes for bubbl3 to ask for: activating bubbl3 for your site in Mindbody is what lets bubbl3 read it.
Events
What bubbl3 receives
| Event in Mindbody | In bubbl3 |
|---|---|
client.created | New lead. A new client: matched, labelled and, if you chose one, enrolled in the source's workflow. |
appointmentBooking.created, classRosterBooking.created | New lead. A booking, enrolled the same way. For a client bubbl3 already has, also "Appointment booked". |
client.updated with account texts turned off | Opt-out. The contact is opted out in bubbl3 (not copied to your other CRMs). A new client or booking with account texts off is opted out too. |
What bubbl3 writes back
Nothing. A STOP in bubbl3 isn't written back to Mindbody yet.
Sending rules that still apply
Mindbody never texts anyone itself. What it sends bubbl3 can start the lead source's workflow, and every workflow text goes through the same checks as a text you send from bubbl3. Nothing in Mindbody can turn them off.
- Consent. When you connect Mindbody or create a lead source, you confirm that everyone you send to bubbl3 has agreed to receive texts from you, so its contacts can be texted straight away. bubbl3 never texts a contact who opted out, and a workspace set to text only opted-in contacts texts only them.
- Opt-out. Replying STOP opts a contact out at once.
- Quiet hours. No texts from 8:00 PM to 9:00 AM in the contact's own time zone (from the phone's area code). A text due then waits until the morning.
- Pacing. Each line texts at most 15 new contacts an hour and 50 a day (fewer while a new line warms up), and spaces texts 20 to 90 seconds apart. A big import or batch is queued and sent as the limits allow, never dropped.
- First messages. Until a contact replies, a text can't include links, photos or files, phone numbers or email addresses, must be 300 characters or fewer, and at most 3 texts go out.
What Mindbody is told when bubbl3 doesn't send
Mindbody has nothing to write a refusal to. You see it in bubbl3: on the message, or on the workflow run's step.
| Reason | Code | What you see |
|---|---|---|
| A link before the contact replies | pre_reply_link_blocked | Not sent: "Links can't be sent until the contact replies" |
| A photo or file before the contact replies | pre_reply_media_blocked | Not sent: "Photos and files can't be sent until the contact replies" |
| A phone number before the contact replies | pre_reply_phone_blocked | Not sent: "Phone numbers can't be sent until the contact replies" |
| An email address before the contact replies | pre_reply_email_blocked | Not sent: "Email addresses can't be sent until the contact replies" |
| A first message that is too long | pre_reply_too_long | Not sent: "First messages must be 300 characters or fewer" |
| Too many texts without a reply | pre_reply_message_limit | Not sent: "Already sent 3 texts without a reply. Wait for the contact to reply" |
| The same text to too many people today | identical_text_limit | Not sent: "This exact text went to 20 people from this line today" |
| The line is paused after unanswered texts | unanswered_streak_limit | Not sent: "This line is paused after too many unanswered texts" |
| The contact opted out | contact_opted_out | Not sent: "The contact opted out of texts" |
| The workspace texts only opted-in contacts | consent_required | Not sent: "This workspace only texts contacts who opted in" |
| No line can reach the contact | line_unavailable | Not sent: "bubbl3's line for this contact isn't available" |
| Quiet hours | quiet_hours | Held: "Scheduled for 9:00 AM America/Chicago, quiet hours" |
| The line's daily limit | daily_new_contact_cap | Held: "Scheduled for Oct 15, 9:00 AM America/Chicago: today's limit for this line is reached" |
| The line's hourly limit of new contacts | hourly_new_contact_cap | Held: "Scheduled for 2:00 PM America/Chicago: this hour's limit of new contacts for this line is reached" |
The numbers are the default limits; a line's own limits change them. bubbl3's other checks (no phone number, a number that doesn't match) have their own plain reasons.
Limits and known gaps
- Going live needs Mindbody's approval of bubbl3, so the tile may say "Coming soon" until then.
- bubbl3 calls Mindbody only when you connect and test.
- A site already connected in another bubbl3 workspace is held until bubbl3's team approves it.
- At most 5 failed staff-login checks an hour per site, across all workspaces; each failure stops counting an hour after it happened.
- If Mindbody starts account texts off for clients nobody asked, those clients are opted out in bubbl3 too. Check a new client's setting in Mindbody before you rely on it for texting.
Troubleshooting
- "Mindbody didn't accept that staff login for the site". Use a login for this site. After 5 failures in an hour, bubbl3 waits before checking again.
- "Too many failed logins for this Mindbody account". Wait for the time shown, then try once more with a working login.
- "Mindbody didn't let bubbl3 read that site". Activate bubbl3 for the site in Mindbody first.
- "Waiting for bubbl3 to confirm this account is yours". The site is already connected in another bubbl3 workspace. bubbl3's team checks before turning it on here; you don't need to reconnect.