Skip to content

Webhook limits

Route Acuity booking events through one operational receiver.

Aculio cuts down fragile Zapier-style webhook sprawl by centralizing Acuity appointment events for each workspace.

Connect AcuityView pricing
Diagram: four Acuity appointment events flow into one Aculio receiver, which routes them to waitlist workflows and SMS automation.

Acuity appointment events

  • scheduled
  • rescheduled
  • canceled
  • changed

Aculio receiver

One consolidated endpoint per workspace

Acuity webhook capacity4 of 25 used

Example workspace

  • Waitlist workflows
  • SMS automation

How Aculio works around the 25-webhook limit

One receiver takes every booking change. Your workflows react to it inside Aculio instead of each needing its own hook.

  1. 1

    Aculio registers appointment scheduled, rescheduled, canceled, and changed events through a consolidated receiver.

  2. 2

    The API reports Acuity webhook capacity, so teams can see the 25-hook ceiling before they hit it.

  3. 3

    Internal routing lets waitlist workflows react to booking changes without a separate external integration for each workflow.

  4. 4

    Webhook signatures can be verified when a signing secret is configured.

  5. 5

    Once events are centralized, route them into advanced SMS automation for waitlist offers, reminders, and two-way replies without adding more external hooks.

Native Acuity webhooks compared with Acuity + Aculio

FeatureNative Acuity SchedulingAcuity + Aculio
Webhook limitsLimited to a maximum of 25 native webhooks.Unlimited. Booking events are multiplexed through one webhook router.
Per-workflow hooksEach external workflow needs its own integration.Waitlist and SMS workflows react to the same centralized events.

Free trial

Try Aculio free for 14 days.

No credit card required. Connect Acuity Scheduling and keep your existing booking flow.