Acuity Scheduling recipes
Text clients when they book, reschedule or cancel an Acuity appointment.
Two recipes for Acuity Scheduling. Each names its trigger and the BlueBot step, lists the fields to map and says how to test it with your own number before anyone else gets a text.
How Acuity Scheduling connects
- : BlueBot’s Zapier app has a Send Text action and instant triggers for incoming texts and every change of state.
Confirm new appointments
| Part | What it is |
|---|---|
| Trigger | When a client books an appointment in Acuity |
| Action | BlueBot’s Send Text action |
| Connects through |
Steps
- Start a Zap with Acuity Scheduling’s trigger for a new appointment.
- Add BlueBot’s Send Text action and map the client’s phone to To.
- Write the text with the appointment type and time mapped in.
Map the fields
| BlueBot field | Map it to |
|---|---|
| To | The person’s mobile number from Acuity Scheduling. US numbers can leave off the +1. |
| Text | Hi {{first_name}}, you’re booked for a {{appointment_type}} on {{date}} at {{time}}. Reply here if you need to change it. |
{{first_name}} in the text | Acuity Scheduling’s first name field. |
{{appointment_type}} in the text | Acuity Scheduling’s appointment type field. |
{{date}} in the text | Acuity Scheduling’s date field. |
{{time}} in the text | Acuity Scheduling’s time field. |
| Metadata | source set to acuity-scheduling, and record_id set to the record’s id, so the status and reply webhooks for this text can find the record again. |
| Service | Auto, the default: iMessage when the person uses it, otherwise SMS through your iPhone. |
Test it
Put your own number in To and press Test step. A text arrives on your phone from your own number, and Zapier shows the message BlueBot returned with state: "queued". Then map Acuity Scheduling’s field back into To and turn the Zap on.
Let clients know a change went through
| Part | What it is |
|---|---|
| Trigger | When an appointment is rescheduled or canceled in Acuity |
| Action | BlueBot’s Send Text action |
| Connects through |
Steps
- Start one Zap with Acuity Scheduling’s trigger for a rescheduled appointment and another for a canceled one.
- Add BlueBot’s Send Text action to each and map the client’s phone to To.
- Write a text for each that gives the new time or a link to book again.
Map the fields
| BlueBot field | Map it to |
|---|---|
| To | The person’s mobile number from Acuity Scheduling. US numbers can leave off the +1. |
| Text | Hi {{first_name}}, your appointment is now {{date}} at {{time}}. See you then. |
{{first_name}} in the text | Acuity Scheduling’s first name field. |
{{date}} in the text | Acuity Scheduling’s date field. |
{{time}} in the text | Acuity Scheduling’s time field. |
| Metadata | source set to acuity-scheduling, and record_id set to the record’s id, so the status and reply webhooks for this text can find the record again. |
| Service | Auto, the default: iMessage when the person uses it, otherwise SMS through your iPhone. |
Test it
Put your own number in To and press Test step. A text arrives on your phone from your own number, and Zapier shows the message BlueBot returned with state: "queued". Then map Acuity Scheduling’s field back into To and turn the Zap on.
Before you turn it on
- Text only people who asked to hear from you. Anyone who replies STOP goes on your stop list, and BlueBot cancels texts to them.
- A text that can’t go yet waits with a hold rather than failing: quiet hours, your Mac away, a daily limit.
- on the integrations page says what else the two do together.