Special workflows for Acuity Scheduling.
Each scenario shows the trigger, the Volimox handoff, and the human checkpoint. These are concrete workflow blueprints, not a claim that every connection is live today.
Appointment to prepared lead
Bring appointment details and intake answers into the Volimox handoff.
Starts when
A new Acuity appointment is booked with the required service details.
Result
The appointment arrives with the context needed for a prepared service handoff.
Volimox workflow
- 01Volimox reads the appointment, intake answers, and contact details.
- 02Volimox creates or updates the matching lead with the scheduled time.
- 03The operator reviews payment, location, and special-request fields before service.
Human checkpoint
Sensitive or incomplete intake fields are flagged for review instead of guessed.
Canceled appointment to recovery
Give the team a clear recovery path when an appointment is canceled or moved.
Starts when
A linked Acuity appointment is canceled or rescheduled.
Result
Canceled appointments become recoverable work instead of silent churn.
Volimox workflow
- 01Volimox updates the lead and records the original appointment state.
- 02Volimox creates a recovery task with the customer preference and reason when available.
- 03The operator chooses a new slot or closes the follow-up with a reason.
Human checkpoint
The operator controls whether the customer receives a new link, a call, or no message.
Supported triggers and actions.
A trigger starts the workflow. An action is the controlled operation Volimox performs after the rules pass.
Triggers
- Appointment booked
- Appointment canceled
- Appointment rescheduled
Actions
- Create appointment
- Update appointment
- Find appointment
Detailed connection code.
This server-side TypeScript reference follows the same connection → action → mapped input pattern used by modern automation platforms. Provider credentials remain inside the approved connection; browser code never receives them.
TypeScript · server only
Create an appointment
import { createZapierSdk } from "@zapier/zapier-sdk"
const zapier = createZapierSdk({
apiKey: process.env.ZAPIER_API_KEY,
})
export async function runAcuitySchedulingAction() {
const { data: connection } = await zapier.findFirstConnection({
app: "acuity-scheduling",
owner: "me",
})
if (!connection) {
throw new Error("No approved Acuity Scheduling connection was found")
}
const result = await zapier.runAction({
app: "acuity-scheduling",
action: "create_appointment",
connection: connection.id,
input:
{
"calendarId": "{{env.ACUITY_CALENDAR_ID}}",
"appointmentTypeId": "{{env.ACUITY_APPOINTMENT_TYPE_ID}}",
"datetime": "{{lead.requestedStartIso}}",
"firstName": "{{lead.firstName}}",
"lastName": "{{lead.lastName}}",
"email": "{{lead.email}}",
"phone": "{{lead.phone}}"
},
})
return result.data
}Connection setup.
The setup path is specific to the provider. We will never ask you to paste credentials into a public page.
Scoped API token
A reviewable connection, step by step.
- 01Acuity administrator token
- 02Select appointment calendars
- 03Confirm customer-data scope
This app is cataloged and its workflow contract is defined. We will enable the connection after provider access and sandbox verification.
Related apps