Short answer: Drop the "Acuity Scheduling → Cancel Appointment" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
Cancel Note cancelNote | string | Optional | Cancel Note |
{"appointmentId": "{{trigger.appointmentId}}","cancelNote": "{{trigger.cancelNote}}"}
{"id": 12345,"canceled": true}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.