ActionAcuity SchedulingUpdated May 2026

How do I fetch a single Acuity appointment?

Short answer: Drop the "Acuity Scheduling → Get Appointment" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Acuity Scheduling actions

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Appointment ID appointmentId	string	Required	Appointment ID

Sample request

{
  "appointmentId": "{{trigger.appointmentId}}"
}

Returns

{
  "id": 12345,
  "type": "Consultation",
  "email": "john@example.com",
  "calendar": "Main",
  "datetime": "2026-04-15T14:00:00",
  "lastName": "Doe",
  "firstName": "John"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Get Appointment.

Any of these apps can fire this action as part of a workflow.

Gmail → Acuity Scheduling

1 Gmail triggers

Slack → Acuity Scheduling

13 Slack triggers

Google Sheets → Acuity Scheduling

2 Google Sheets triggers

HubSpot → Acuity Scheduling

18 HubSpot triggers

FAQ

Questions about Get Appointment.

What does the Get Appointment action do in Acuity Scheduling?

Returns the full appointment record by ID — client, time, duration, payment status, intake form answers, calendar assignment. The standard lookup for workflows that need fresh state of an appointment whose ID was captured upstream (e.g., from a webhook a few minutes ago).

What inputs does Get Appointment require?

Required: Appointment ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Acuity Scheduling returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Get Appointment support batch operations?

Yes. Run Get Appointment inside a Loop node to process arrays. Tiny Command handles Acuity Scheduling's rate limits automatically so you don't have to throttle manually.

More actions