Zenoti
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | Clinics and wellness | Enter your Zenoti account details in bubbl3 |
Zenoti 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
Zenoti runs larger spa, med spa and salon chains. Connecting a center sends each new booking and each new guest to bubbl3, from the webhook automation you set up in Zenoti. Each one:
- becomes (or updates) a contact, matched on phone and email, keeping only the minimum guest details (see below);
- goes through the connection's lead source, which sets its labels, owner, consent and workflow;
- for a guest bubbl3 already has, a booking also counts as the conversion event Appointment booked. Each appointment in a group booking is its own lead.
bubbl3 never books or messages anything in Zenoti.
Setup
Zenoti's webhooks need a Zenoti subscription that includes them.
- In Zenoti, open Configuration, Integrations, Apps and make an API key for bubbl3.
- In bubbl3, open Settings, Integrations, choose Zenoti and enter the center ID and the key. bubbl3 checks it can read the center.
- On the connection page, the Patient data card shows the connection's own webhook address (people with full access to integrations can see it). Paste it into a Zenoti automation for new appointment groups and new guests. Keep it private: reconnecting makes a new one.
- Set the lead source's consent and workflow.
| What you enter | Where to find it |
|---|---|
| Center ID | In Zenoti, Configuration, Centers: the ID is on the center's page |
| API key | In Zenoti, Configuration, Integrations, Apps |
Disconnect
Disconnect from the connection page in Settings, Integrations, then remove the automation in Zenoti.
- Stops at once: bubbl3 refuses deliveries to the old webhook address, and the lead source is paused.
- Deleted at once: your API key.
- Stops working at once: the connection's webhook key. bubbl3 refuses anything sent to the old address; the key stays sealed on the disconnected connection, where nothing reads it.
- Kept: contacts made from Zenoti, with their messages, labels and consent, and only the minimum details. The paused lead source stays. The connection's account details (the center it names) stay on the disconnected connection.
- Deleted later: stored deliveries are deleted 30 days after they arrived.
Data shared
From Zenoti to bubbl3: new bookings and guests. bubbl3 keeps only first and last name, mobile number, email and the appointment's start.
From bubbl3 to Zenoti: nothing.
Patient data
Zenoti 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
Zenoti API keys have no scopes: the key acts for your center.
Events
What bubbl3 receives
| Event in Zenoti | In bubbl3 |
|---|---|
AppointmentGroup.Created | New lead. One booking per appointment in the group: matched, labelled and, if you chose one, enrolled in the source's workflow. For a guest bubbl3 already has, also "Appointment booked". |
Guest.Created | New lead. A new guest, enrolled the same way. |
What bubbl3 writes back
Nothing. A STOP in bubbl3 isn't written back to Zenoti.
Sending rules that still apply
Zenoti 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 Zenoti can turn them off.
- Consent. When you connect Zenoti 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 Zenoti is told when bubbl3 doesn't send
Zenoti 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
- Zenoti's automations are set up in Zenoti, so bubbl3 can't add or remove them for you.
- bubbl3 calls Zenoti only when you connect and test.
Troubleshooting
- Nothing arrives. Check the automation uses the address from the Patient data card, and that you haven't reconnected since.
- Bookings arrive but nobody is texted. The person opted out, or the lead source has no workflow chosen.