Acuity Scheduling's REST API lets another system read and create appointments, clients, and availability, and its webhooks fire the moment a booking, reschedule, or cancellation happens, so a connected system can react right away instead of checking Acuity's calendar on a schedule. Common connections, Zoom, Google Calendar, and a handful of payment processors, already come built in. Anything outside that short list, a franchise system, a specific CRM, a different practice-management tool, usually means working with the API or webhooks directly.
Zoom. A video meeting link gets generated and attached to an appointment automatically when Zoom is connected, no manual step for either the business or the client.
Google Calendar. Connected separately from the API, through Acuity's own account settings, this is the two-way sync covered on a given calendar: availability checked, bookings written.
Payment processors. Square, Stripe, and PayPal connect natively so a deposit or full payment can be collected right at booking, with the transaction tied to the appointment record.
Zapier. Acuity Scheduling has a Zapier app covering common single-step triggers, new appointment created, appointment canceled, enough for straightforward connections to a wide range of other tools without custom code.
The native list covers the common cases well. It stops helping the moment a business needs two-way sync with something that isn't on it, a franchise management platform, a CRM with no Zapier trigger for Acuity, or a practice-management system the business already runs day to day. At that point, there's no app to install, the work is a direct API or webhook connection.
Bulk historical data is the other common wall. Webhooks only fire for events going forward from when they're set up, so pulling in months or years of past appointments and client history, something a business switching systems usually needs, means a one-time bulk pull through the API instead.
A franchise platform, a specialized CRM, or a practice-management tool with no Acuity Zapier trigger gets connected directly through the API instead, keeping client and appointment records current on both sides.
A business running several Acuity Scheduling calendars across locations gets one combined appointment and revenue feed pulled through the API, instead of someone exporting and merging each calendar by hand.
Tell us what it is, and we'll sort out whether the API gets you there directly.
The native integrations handle Zoom, Google Calendar, and a handful of payment processors well. Everything else is a build, not an install, and that's exactly where we come in. Acuity Scheduling is just one tool this applies to. Any system your business runs that the common integrations never quite reach is worth the same question.
Let's talk →Yes. Acuity Scheduling can send a webhook notification the moment an appointment is created, rescheduled, or canceled, letting a connected system react immediately instead of checking for changes on a schedule.
Yes, natively. Once connected, Acuity generates and attaches a Zoom meeting link to an appointment automatically, for both the business and the client.
Yes, Acuity Scheduling has its own Zapier app covering common triggers like a new or canceled appointment, which is usually the fastest path for a straightforward single-step connection.
For direct API or webhook work, generally yes, since it means writing and hosting code rather than configuring an app. Zapier covers the simpler single-step cases without one.