--- title: "Acuity Scheduling Integration" description: "Book, reschedule, and cancel appointments, check open availability, and keep clients, appointment types, and intake forms in sync through the Acuity Scheduling API." url: https://flowrunner.ai/integrations/acuity date_modified: 2026-08-01T02:40:32-07:00 --- # Acuity Scheduling [Scheduling](https://flowrunner.ai/integrations/category/project-management-productivity) Book, reschedule, and cancel appointments, check open availability, and keep clients, appointment types, and intake forms in sync through the Acuity Scheduling API. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 1 trigger · 17 actions · Basic auth · available [Acuity Scheduling website](https://acuityscheduling.com/) · [Platform Documentation](https://developers.acuityscheduling.com/reference) · Capability data verified 2026-07-14 1. On New Appointment fires when a client books through Acuity 2. Agent reads the client details, appointment type, and any intake form answers 3. Agent confirms the appointment type and calendar match the requested service 4. Agent checks the intake answers against the flags that require staff review 5. Agent creates or enriches the client record in the CRM with the booking 6. Agent posts the booking and prep notes to the assigned staff member 7. A booking whose intake answers trip a review flag is held for a staff decision before confirmation goes out ## What This Integration Enables FlowRunner agents use Acuity Scheduling to turn a self-service booking into a fully prepared appointment across your stack. An agent can read what a client booked, mirror it into a CRM or a staff calendar, attach the intake data, and notify the right person with context. It can check open dates and times and confirm a specific slot before booking on a client behalf, so it never books into a slot that just filled. What it does not do is push every booking through untouched. When an intake answer signals a case that needs a human, the agent stops and asks. ### Without FlowRunner **Manual CRM entry**: Someone copies each new booking into the CRM by hand after it lands **No context for staff**: The assigned person sees a calendar block with no client history or prep notes **Intake read too late**: Intake answers that need attention are noticed only when the appointment starts ### With FlowRunner **Booking synced on arrival**: The client record and appointment are updated the moment the booking fires **Prep in the notification**: Staff get the client details and prep notes with the booking alert **Flagged intake stops early**: Intake answers that need review pause the booking for a human before confirmation ## Use Case Scenarios ### Booking-to-CRM Onboarding A client books a consultation through the Acuity link. On New Appointment fires. The agent reads the appointment type, the calendar, and the intake form answers. It creates or updates the client record in the CRM with Create Client details mirrored across, logs the appointment, and creates a matching event on the staff member calendar. It then notifies the assigned person with the client history and the prep notes the intake supplied. The client is booked, the record is current, and the staff member is prepared without anyone retyping a thing. ### Availability-Aware Rebooking A client asks to move an appointment through a separate channel. The agent calls Get Availability Dates for the appointment type, then Get Availability Times for the chosen day, and confirms the exact slot with Check Times before it commits. It calls Reschedule Appointment, updates the CRM, and sends the client the new confirmation. Because the agent confirms the slot is still open at the last step, it never double-books. ### Intake Review Gate A new-patient booking comes in with an intake form. The agent reads the answers and matches them against the conditions that require a clinician or manager to look before the appointment is confirmed. Routine bookings confirm automatically. A booking that trips a flag pauses and routes to the reviewer, who decides whether to confirm, adjust the appointment type, or reach out to the client first. ## Human-in-Loop Highlight When On New Appointment fires with intake answers that match a review condition, the agent does not send the confirmation and move on. It pauses and routes to the designated reviewer through their preferred channel: "New booking from \[Client\] for \[Appointment Type\] on \[date\]. Their intake answers flagged \[reason\]. Confirm the appointment, change the appointment type, or hold for outreach?" The reviewer decides. The bookings that carry real consequences get a human judgment before the confirmation goes out. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 17 actions ### Appointments 6 - **Create Appointment** Books an appointment for a client against an appointment type and calendar. Used when an agent schedules on the client behalf after qualifying the request in another system. - **Get Appointment** Retrieves a single appointment by ID. Used to read the current time, client, and status before a reschedule or cancellation. - **List Appointments** Returns scheduled appointments with filtering by date range, calendar, appointment type, and client, plus sort direction. Used to find the appointments a workflow needs to act on. - **Reschedule Appointment** Moves an existing appointment to a new time. Used when a client or upstream system requests a change. - **Cancel Appointment** Cancels a booked appointment. Used in cancellation flows driven by client requests or conflicts detected elsewhere. - **Update Appointment** Updates the fields on an existing appointment, such as intake form values or notes. Used to keep the booking accurate as details change. ### Availability 3 - **Check Times** Confirms whether a specific time is actually open before booking. Used as the final guard so an agent never books into a slot that just filled. - **Get Availability Dates** Returns the open dates in a month for an appointment type and calendar. Used to offer a client a set of candidate days. - **Get Availability Times** Returns the open times on a given date. Used after a date is chosen to present bookable slots. ### Appointment Types and Calendars 2 - **List Appointment Types** Lists the appointment types that define what can be booked. Used to resolve the appointment type ID an agent needs before scheduling. - **List Calendars** Lists the calendars that represent staff or resources. Used to route a booking to the right calendar. ### Clients 3 - **Create Client** Creates a client record. Used to register a new client the first time they book through an automated flow. - **List Clients** Returns client records. Used to find an existing client before booking or updating. - **Update Client** Updates a client record. Used to keep contact details current across tools. ### Forms and Account 3 - **List Forms** Lists the intake forms and their field IDs. Used to discover the field IDs an agent must supply when attaching intake data to an appointment. - **List Certificates** Lists discount and gift certificates on the account. Used to audit or reconcile certificate usage. - **Get Me** Returns the connected account details. Used as a connection check. ## Triggers 1 triggers ### Event Triggers 1 - **On New Appointment** Polls Acuity and fires when a new appointment is booked. When it fires, agents read the client and intake details, mirror the booking into a CRM and a staff calendar, attach prep notes, and hold any booking whose intake answers require review. ## Frequently Asked Questions ### What can FlowRunner do with Acuity Scheduling? FlowRunner agents can run Create Appointment, Get Appointment, and List Appointments in Acuity Scheduling, plus 14 more actions. ### Does connecting Acuity Scheduling to FlowRunner require OAuth? No. Acuity Scheduling connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can Acuity Scheduling trigger a FlowRunner workflow automatically? Yes. Acuity Scheduling supports 1 trigger that can start a FlowRunner workflow automatically. **Work at Acuity Scheduling?** This integration exposes Acuity Scheduling to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/acuity. Site index: https://flowrunner.ai/llms.txt