Resources · n8n integration

Acuity Scheduling n8n integrationAutomate Acuity Scheduling with n8n.

Which booking change should start a workflow? The Acuity Scheduling n8n integration is a trigger only: 5 webhook events, split across 2 families, appointment and order. No action node ships with this tool, so writing back to Acuity goes through HTTP Request. Useful if bookings drive your operations.

Try the Acuity Scheduling integration on n8n

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Acuity Scheduling n8n integration actually cover?

Acuity Scheduling reaches n8n through a webhook, meaning a URL that n8n owns and Acuity calls every time something moves on the calendar. The n8n catalogue holds one node for this tool, the Acuity Scheduling Trigger, version 1, carrying 5 events grouped in 2 families. Its job is to start the workflow. What happens next is handled by the other nodes you place after it.

First pattern, the booking becomes a row. appointment.scheduled fires once when a client books a slot, and the workflow appends that booking to Google Sheets, so the week ahead sits in a file the whole team can sort and filter without opening Acuity.

Second pattern, the cancellation reaches a human fast. appointment.canceled pushes the freed slot into a Slack channel where whoever owns the calendar can refill it, and the same branch sends a short rebooking message through Gmail.

Third pattern, paid bookings feed a revenue log. order.completed fires when an order is completed, and the workflow writes one record per order into Airtable, next to the client who placed it.

The catalogue gives this tool a trigger and nothing else. Reading a client list, pushing data back into Acuity, anything beyond listening to events goes through the HTTP Request node, which calls any endpoint of the Acuity API and reuses the credential you already saved in n8n.

One detail worth planning for. appointment.changed is called when the appointment is changed in any way, while appointment.rescheduled is called when it moves to a new time. Two events can describe the same booking, so pick the one that matches the action you actually want to run, or branch on both and deduplicate downstream.

Hosting shapes the rest of the setup, since the trigger needs a URL that Acuity can reach from the outside. On n8n Cloud that part is already handled. On a self-hosted instance it is one more thing to expose properly before the first booking lands, and it is usually what makes people hesitate between the two. The n8n review goes through Cloud against self-hosted on that exact point, with the data question next to it.

Connect

How do you connect Acuity Scheduling to n8n?

  1. 01

    Generate the API key in Acuity

    An Acuity Scheduling account is the starting point. The API key method needs two values, a numeric User ID and an API Key, both of them shown on the Acuity API Quick Start authentication page. Copy them somewhere safe before leaving the page, because you will paste both into the same credential form.

  2. 02

    Or register an OAuth2 app instead

    The trigger also accepts OAuth2. Complete the Acuity OAuth2 Account Registration page, which hands back a Client ID and a Client Secret. Use this route when several people share the n8n instance and you would rather not spread a raw API key around. Either method authenticates the same trigger node.

  3. 03

    Save the credential and activate the workflow

    In n8n, open the Credentials menu and create the Acuity Scheduling credential once, with whichever pair of values you chose. Every workflow can reuse it, and the trigger offers it in a dropdown. Activate the workflow: n8n registers the webhook URL with Acuity at that moment, and events start landing within seconds.

Triggers

What starts an n8n workflow from Acuity Scheduling ?

Acuity Scheduling Trigger is the node that starts a workflow when something happens in Acuity Scheduling. It listens to 5 events, listed below by family. Pick one or several, activate the workflow: n8n registers the webhook on your Acuity Scheduling account.

What you see in n8n

Every event, by family

One row per object, one chip per action. The event to tick in the node is object.action; hover a chip to read exactly when it fires.

appointment.*4
  • appointment.
    • canceled
    • changed
    • rescheduled
    • scheduled
order.*1
  • order.
    • completed

Configuration notes

01Set up the Acuity Scheduling TriggerThis node listens to your Acuity account and hands the workflow an item every time the chosen event happens. n8n registers its webhook URL, the address Acuity calls, when you switch the workflow on, so nothing arrives while the workflow sits inactive in the editor.

This node listens to your Acuity account and hands the workflow an item every time the chosen event happens. n8n registers its webhook URL, the address Acuity calls, when you switch the workflow on, so nothing arrives while the workflow sits inactive in the editor.

Key parameters

  • Event: the Acuity event the node listens to, picked from the 5 values in the catalogue. There is no wildcard value that catches everything, so each event you care about is selected on purpose.
  • Resolve Data: off by default, the webhook payload carries only the ID of the object. Switch it on and n8n resolves the data automatically, which saves you a lookup before the next node.
Use cases
a first workflow that logs every booking somewhere readable, built once with Resolve Data on so the fields are there from the start.
02React to appointment eventsFour of the 5 events describe the life of a single appointment, which makes this family the one most workflows start from. Each of them arrives on its own, so a booking that gets moved then dropped produces separate executions you can treat differently.

Four of the 5 events describe the life of a single appointment, which makes this family the one most workflows start from. Each of them arrives on its own, so a booking that gets moved then dropped produces separate executions you can treat differently.

Key parameters

  • Event: appointment.scheduled is called once when an appointment is initially booked. appointment.changed is called when the appointment is changed in any way. appointment.rescheduled is called when it moves to a new time. appointment.canceled is called whenever an appointment is canceled.
When to use it
whenever the calendar itself is the source of truth for another system, a spreadsheet, a CRM, a channel.
Use cases
a prep checklist created on appointment.scheduled, and a cleanup branch on appointment.canceled that archives it.
03React to completed ordersThe order family holds a single event and covers the money side rather than the calendar side. It fires when an order is completed in Acuity, which is the moment a paid booking or a package purchase becomes final.

The order family holds a single event and covers the money side rather than the calendar side. It fires when an order is completed in Acuity, which is the moment a paid booking or a package purchase becomes final.

Key parameters

  • Event: order.completed, called when an order is completed.
  • Resolve Data: particularly worth switching on here, since the raw payload carries the object ID alone and a finance workflow usually needs the order details themselves.
When to use it
when accounting, and not scheduling, is the thing being automated, or when a paid booking has to follow a different path from a free one.
Use cases
each completed order lands in a monthly sheet, and a copy of the same item goes to whoever reconciles payments at the end of the month.
Need help

Need help automating Acuity Scheduling with n8n?

A person reads every message.

FAQ

Acuity Scheduling and n8n, the questions that come up

01Is the Acuity Scheduling n8n integration free?
Yes on the n8n side. The Acuity Scheduling Trigger ships with n8n, so there is nothing to install and nothing extra to pay to use it. That holds on n8n Cloud, the hosted offer run by n8n, and on a self-hosted instance under the Community Edition and its Sustainable Use license. A workflow behaves the same way in both places, and the same credential works in both. What an Acuity Scheduling plan costs on its own is a separate question and is not covered here, since the n8n catalogue says nothing about it.
02What credentials does the Acuity Scheduling Trigger need?
Two authentication methods are supported, and you only need one. The API key method asks for a numeric User ID and an API Key, both available from the Acuity API Quick Start authentication instructions. The OAuth2 method asks for a Client ID and a Client Secret, which come from the Acuity OAuth2 Account Registration page. An Acuity Scheduling account is required either way. The credential is created once in the Credentials menu of n8n, and every workflow that needs Acuity picks it from the node dropdown rather than repeating the values.
03What are the limits of this integration in n8n?
It depends on what you need. The n8n catalogue lists this tool as a trigger, with 5 events across 2 families, appointment and order, and no action node alongside it. So anything that is not listening to events, reading records or sending data back to Acuity, goes through the HTTP Request node. That node calls any endpoint of the Acuity API and reuses the credential you already configured, which means no second login and no separate key to manage. Most workflows end up mixing the trigger with a couple of HTTP Request calls.
04Does the Acuity Scheduling Trigger react in real time?
Yes. This trigger works by webhook, meaning Acuity calls a URL that belongs to n8n instead of n8n asking Acuity for news on a schedule. n8n registers that URL with Acuity when the workflow is activated, and from then on each event arrives within seconds, with no polling and no interval to tune. The practical consequence is that an inactive workflow receives nothing, so a change made while you were testing in the editor will not replay itself once you switch the workflow on.
05n8n or Make for Acuity Scheduling?
It depends on four criteria. Hosting first: Make is a hosted platform with no self-hosting option, while n8n runs on your own server or on n8n Cloud. Data control follows from that, since a self-hosted instance keeps booking data on infrastructure you own. Cost model next: Make bills per operation, which matters when a busy calendar fires events all day. Visual logic last, both editors are node based and the preference is genuinely personal. Neither answer is wrong, the criteria just weigh differently depending on volume and on who runs your servers.
Same platform

Other docs you might need on this stack.

Browse all integrations