Scheduling & Booking · Integration
Acuity Scheduling
Add Acuity Scheduling to your product for your customers, and give your AI agents governed access to it.
Acuity models a booking as an appointment of a particular appointment type against a calendar, and availability is computed rather than stored, which is exactly why it has to be read at the moment somebody is choosing and not cached for the afternoon. Appointment types carry their own duration, padding, price and the calendars allowed to serve them, so an integration that ignores types will cheerfully offer a slot nobody can actually work. Intake forms are attached to the appointment and their answers come back with it, which is usually where the information your product genuinely needs is sitting. Bookings, reschedules, cancellations and changes each raise their own webhook, so a cancellation made inside Acuity reaches your product instead of being discovered when somebody fails to turn up. Each account connects itself, so working hours, blocked time and timezone stay the customer's own configuration.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each customer connect their own Acuity account so bookings land on the calendars and working hours they already set up.
Read availability at the moment somebody is choosing, since a slot that was free ten minutes ago is not a promise.
Book against the right appointment type, so duration, padding and price come from the customer's configuration rather than yours.
Read intake form answers alongside the appointment, because that is where the detail a booking is actually about lives.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent finds the next slot that fits and books it in the customer's own account, with the appointment id recorded.
An agent reschedules or cancels within scoped permissions and reports what the client will see.
An agent summarises tomorrow's appointments with each one's intake answers attached.
Example prompt
What is on the calendar tomorrow, and did anybody book without finishing the intake form?
Set up Acuity Scheduling in 4 steps
- 01Enable the Acuity Scheduling connector in your fastn dashboard.
- 02Have each customer authorise their own Acuity account, so their calendars, working hours and blocked time stay theirs.
- 03Map the appointment types and intake form fields your product uses, then subscribe to the booking, reschedule and cancellation webhooks.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Acuity Scheduling integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Acuity Scheduling integration without building it. Your customers connect their own Acuity Scheduling account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Acuity Scheduling update is not your on-call problem.
- One integration serves your product and your agents. The same governed Acuity Scheduling connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Calendly
Google CalendarWorks well with
HoneyBookOften used alongside
Tools the same teams tend to run next to Acuity Scheduling, across other categories.
Slack
Microsoft Teams
Twilio
AircallAcuity Scheduling integration FAQ
How do I add an Acuity Scheduling integration to my product?
Enable the Acuity Scheduling connector in your fastn dashboard, then let each customer authenticate their own Acuity Scheduling account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Acuity Scheduling client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Acuity Scheduling account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Acuity Scheduling account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Acuity Scheduling integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent finds the next slot that fits and books it in the customer's own account, with the appointment id recorded.
Who maintains the Acuity Scheduling integration?
fastn does. When Acuity Scheduling changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in Acuity Scheduling automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in Acuity Scheduling?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the Acuity Scheduling integration?
A common starting point: let each customer connect their own Acuity account so bookings land on the calendars and working hours they already set up. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Acuity Scheduling integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Acuity Scheduling does not change your per-connector cost. You can start free with 3 connected accounts.
Add Acuity Scheduling to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.