Healthie
| Status | Kind | How you connect |
|---|---|---|
| Coming soon | Clinics and wellness | Enter your Healthie account details in bubbl3 |
Healthie 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
Healthie runs telehealth and nutrition practices. Connecting it sends each new appointment and each new patient to bubbl3 as it's made. Each one:
- becomes (or updates) a contact, matched on phone and email, keeping only the minimum patient details (see below);
- goes through the connection's lead source, which sets its labels, owner, consent and workflow;
- for a patient bubbl3 already has, a booking also counts as the conversion event Appointment booked.
bubbl3 never books, changes or messages anything in Healthie.
Setup
- Ask Healthie support for an API key for bubbl3 (Healthie issues them on request).
- In bubbl3, open Settings, Integrations, choose Healthie and paste the key. bubbl3 checks it with one read call and registers its webhook.
- Set the lead source's consent and workflow. "Not sure" records new patients' consent as unknown; they can still be texted, because you confirmed when connecting that everyone you send has agreed to receive texts.
| What you enter | Where to find it |
|---|---|
| API key | From Healthie support, on request |
Disconnect
Disconnect from the connection page in Settings, Integrations.
- Stops at once: new appointments and patients. bubbl3 deletes its webhook in Healthie, 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 Healthie, with their messages, labels and consent, and only the minimum details. The paused lead source stays. The connection's account details (the Healthie account it names) stay on the disconnected connection.
- Deleted later: stored deliveries are deleted 30 days after they arrived.
Data shared
From Healthie to bubbl3: each new appointment (its date and patient) and each new patient, read back with your key. bubbl3 keeps only first and last name, phone, email and the appointment time.
From bubbl3 to Healthie: only bubbl3's webhook.
Patient data
Healthie 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
Healthie API keys have no scopes: the key acts as your practice. bubbl3 uses it only to read your organization, register its webhook and read the record each webhook names.
Events
What bubbl3 receives
| Event in Healthie | In bubbl3 |
|---|---|
appointment.created | New lead. A booking: matched, labelled and, if you chose one, enrolled in the source's workflow. For a patient bubbl3 already has, also "Appointment booked". |
patient.created | New lead. A new patient, matched and enrolled the same way. |
What bubbl3 writes back
Nothing. Healthie only sends bookings and patients to bubbl3. A STOP in bubbl3 isn't written back.
Sending rules that still apply
Healthie 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 Healthie can turn them off.
- Consent. When you connect Healthie 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 Healthie is told when bubbl3 doesn't send
Healthie 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
- bubbl3 reads each record once, at most 5 calls a second, and waits when Healthie says to.
- Healthie's opt-outs aren't sent to bubbl3; contacts who reply STOP are opted out in bubbl3.
Troubleshooting
- "The provider didn't accept these credentials". Check the key with Healthie support.
- Bookings arrive but nobody is texted. The person opted out, or the lead source has no workflow chosen.