Integrations
Start a Duaer workflow with Acuity Scheduling Trigger
In Duaer, Acuity Scheduling Trigger starts a workflow when Acuity Scheduling sends an event. It can listen for 5 events, such as appointment.canceled, appointment.changed, appointment.rescheduled, and 2 more.
Start a Duaer workflow with Acuity Scheduling Trigger
- On the Duaer canvas, open the node panel, search for Acuity Scheduling Trigger, and add it as the first node.
- Under Authentication, choose API Key or OAuth2, then pick or create the matching credential (Acuity Scheduling API or AcuityScheduling OAuth2 API) in Credential to connect with.
- Pick the events that should start a run, for example appointment.canceled or appointment.changed.
- Check Resolve Data on the node.
- Select Execute step, then cause a real event in Acuity Scheduling to capture a sample. Publish the workflow so Duaer registers the webhook and starts a run for every event.
Events that start a Duaer workflow with Acuity Scheduling Trigger
- appointment.canceled: Is called whenever an appointment is canceled.
- appointment.changed: Is called when the appointment is changed in any way.
- appointment.rescheduled: Is called when the appointment is rescheduled to a new time.
- appointment.scheduled: Is called once when an appointment is initially booked.
- order.completed: Is called when an order is completed.
Acuity Scheduling Trigger parameters in Duaer
- Resolve Data: By default does the webhook-data only contain the ID of the object.
Questions
Which Acuity Scheduling Trigger events can start a Duaer workflow?
Duaer's Acuity Scheduling Trigger can listen for 5 events, including appointment.canceled, appointment.changed, appointment.rescheduled, appointment.scheduled, and order.completed. Pick one or more on the node.
Does Acuity Scheduling Trigger run before the Duaer workflow is published?
Only while you test with Execute step. Duaer registers the Acuity Scheduling Trigger webhook for production runs after you publish.
Which credential does Acuity Scheduling Trigger use in Duaer?
Duaer's Acuity Scheduling Trigger uses Acuity Scheduling API or AcuityScheduling OAuth2 API, depending on the method you choose under Authentication.
In this section
Built-in integrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Triggers start a workflow. Actions run a step after it has started.
IntegrationsRisks of community nodes in Duaer
Before you install a community node in Duaer, know the code comes from a source the instance admin trusts, and know what permissions it gets.
IntegrationsTroubleshoot community nodes in Duaer
When a Duaer community node will not install or run, check the version, permissions, and node docs, then the instance logs.
IntegrationsMake custom API calls for an app in Duaer
When a Duaer app node does not expose the API you need, use HTTP Request and reuse that app’s saved authentication.
IntegrationsIntegrations in Duaer
Built-in triggers, actions, and credentials in Duaer. Community nodes are extra packages. Custom operations reuse saved authentication with HTTP Request.
CredentialsBuilt-in credentials in Duaer
Per-service credential notes for Duaer built-ins. The create flow is in the credentials overview; node docs link to the matching service page.
Create nodesCreate a custom node for Duaer
Write a node package for Duaer when built-in nodes and custom operations are not enough and you will reuse the step.