What makes Acuity Scheduling easy or hard to automate
Acuity was built for appointment businesses: therapists, salons, fitness studios, consultants, tutors and clinics. Appointment types can have their own intake forms, packages, deposits and coupons, so a single booking often holds most of what staff need to know before the visit.
Webhooks are simple. Acuity posts a form-encoded request with the action, the appointment ID, the calendar ID and the appointment type ID. It does not include the client’s name, time or answers. Your workflow verifies the x-acuity-signature header, then calls the API to fetch the appointment. That extra call is easy, but it means every automation needs API access.
API access is where planning matters. Direct API calls have been limited to Acuity’s top plan tier, and custom agents and n8n workflows that read appointments depend on it.
The AI layer
Appointment businesses lose time to the same problems: unread intake forms, no-shows and back-and-forth about times. AI helps with each:
- Reading intake. A model condenses intake answers into the three or four things the provider must know, such as goals, contraindications or a returning concern.
- Conversations around the booking. Replies to reminder texts are messy (“can we do Thursday instead”, “stuck in traffic”). A model classifies them and drafts a response, and code calls the API to reschedule only when a real open slot exists.
- After the visit. Follow-ups, rebooking nudges and review requests get personalized by service and history.
For clinical practices, the model never gives medical advice. It summarizes and routes, and a person decides.
Limits to plan around
- Plan gating. Confirm your plan includes API access before building anything beyond a Zapier or Make connection.
- Thin webhooks. Every event needs a follow-up API call. Handle the case where the appointment was canceled between the webhook and the fetch.
- Duplicate events. Choose either the catch-all
changedevent or the specific events, not both. - HIPAA configuration. HIPAA features and the BAA come with the top Premium plan as of 2026, and connected integrations are your responsibility.
- Time zones. Appointments carry the calendar’s time zone. Convert explicitly before writing reminders, especially for clients booking from other zones.
How Lumeor typically connects it
We receive Acuity webhooks in n8n, verify the signature, fetch the appointment, and branch by action. An LLM step summarizes intake or drafts messages, and Twilio sends texts. Booking agents use a small service that wraps Acuity availability and booking as tools, the same pattern as the home services booking agent guide. Sales teams booking demos rather than appointments are usually better served by Calendly, and reminder flows are covered in the no-show reduction guide.