Acuity Scheduling

Business appsUsername & passwordConnection test available

Book, reschedule and cancel Acuity Scheduling appointments and manage the account's webhook subscriptions.

OCNORA ships 9 typed Acuity Scheduling operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run. Endpoints not covered by a typed node are called at https://acuityscheduling.com/api/v1 through the HTTP node with the same credential.

Before you connect Acuity Scheduling

Authentication
Username & password
Credential
{"user_id", "api_key"}{"user_id": "123456", "api_key": "…"}
Connection test
Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
Prerequisites
  • The numeric user id and API key from Acuity → Settings → Integrations → API. The API key is also the shared secret every delivery is signed with, so rotating it in Acuity means republishing here. Publishing needs MANTLE_APP_PUBLIC_BASE_URL set — it is the address Acuity calls back on, and Acuity accepts only port 443 or 80.

Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.

What you can do with Acuity Scheduling

Operations, grouped by what they do to your data, plus 1 trigger that start a run.

A sample Acuity Scheduling workflow

  1. 1
    Eventtrigger.acuity_scheduling_event
    Start a run when an Acuity Scheduling appointment is booked, rescheduled, canceled or changed.
  2. 2
    Get Appointmentacuity_scheduling.get_appointment
    Fetch one appointment by its numeric id.
  3. 3
    Cancel Appointmentacuity_scheduling.cancel_appointment
    Cancel an appointment, optionally recording it as a client no-show.

An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.

Acuity Scheduling questions

How does OCNORA authenticate with Acuity Scheduling?
With a stored Username & password credential, shaped {"user_id", "api_key"} or {"user_id": "123456", "api_key": "…"}. A connection test can check it when you add it.
What can I automate with Acuity Scheduling?
9 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
What if the Acuity Scheduling operation I need is not listed?
Call https://acuityscheduling.com/api/v1 from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
Are there templates that use Acuity Scheduling?
Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
How are Acuity Scheduling calls controlled?
Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.

See your first Acuity Scheduling workflow run.

Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.