How to connect Acuity Scheduling and Ortto
Create a New Scenario to Connect Acuity Scheduling and Ortto
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Acuity Scheduling, triggered by another scenario, or executed manually (for testing purposes). In most cases, Acuity Scheduling or Ortto will be your first step. To do this, click "Choose an app," find Acuity Scheduling or Ortto, and select the appropriate trigger to start the scenario.

Add the Acuity Scheduling Node
Select the Acuity Scheduling node from the app selection panel on the right.


Acuity Scheduling

Configure the Acuity Scheduling
Click on the Acuity Scheduling node to configure it. You can modify the Acuity Scheduling URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Ortto Node
Next, click the plus (+) icon on the Acuity Scheduling node, select Ortto from the list of available apps, and choose the action you need from the list of nodes within Ortto.


Acuity Scheduling
⚙
Ortto

Authenticate Ortto
Now, click the Ortto node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Ortto settings. Authentication allows you to use Ortto through Latenode.
Configure the Acuity Scheduling and Ortto Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Acuity Scheduling and Ortto Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Ortto
Trigger on Webhook
⚙

Acuity Scheduling
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Acuity Scheduling, Ortto, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Acuity Scheduling and Ortto integration works as expected. Depending on your setup, data should flow between Acuity Scheduling and Ortto (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Acuity Scheduling and Ortto
Acuity Scheduling + Zoom + Ortto: When a new appointment is booked in Acuity Scheduling, a Zoom meeting is created, and the contact information is updated in Ortto.
Acuity Scheduling + Slack + Ortto: When a new appointment is booked in Acuity Scheduling, a Slack notification is sent, and a custom activity event is created in Ortto.
Acuity Scheduling and Ortto integration alternatives

About Acuity Scheduling
Automate appointment scheduling with Acuity inside Latenode. Sync appointments to calendars, send reminders, and update CRMs automatically. Ditch manual data entry and build custom workflows using Latenode’s visual editor and API-first design. Scale your scheduling processes without code or per-step pricing limits.
Similar apps
Related categories
About Ortto
Use Ortto in Latenode to automate personalized marketing campaigns. Trigger emails, SMS, or push notifications based on real-time data from any source. Segment users and update profiles dynamically within Latenode workflows, responding instantly to behavior. Improve engagement by connecting Ortto's segmentation to your Latenode data pipelines.
Similar apps
Related categories
See how Latenode works
FAQ Acuity Scheduling and Ortto
How can I connect my Acuity Scheduling account to Ortto using Latenode?
To connect your Acuity Scheduling account to Ortto on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Acuity Scheduling and click on "Connect".
- Authenticate your Acuity Scheduling and Ortto accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically add new Acuity Scheduling clients to Ortto?
Yes, you can! Latenode's visual builder makes this simple. Trigger workflows based on new appointments, and automatically add clients to Ortto for targeted marketing campaigns. Boost engagement effortlessly.
What types of tasks can I perform by integrating Acuity Scheduling with Ortto?
Integrating Acuity Scheduling with Ortto allows you to perform various tasks, including:
- Add new Acuity Scheduling clients to Ortto as new contacts.
- Update contact information in Ortto when appointments are scheduled.
- Trigger personalized email campaigns based on appointment types.
- Segment clients in Ortto based on their appointment history.
- Send SMS reminders via Ortto before scheduled appointments.
Can I filter Acuity Scheduling appointments based on custom fields?
Yes! Latenode allows advanced filtering using JavaScript blocks. Process only specific appointments based on criteria beyond the standard options.
Are there any limitations to the Acuity Scheduling and Ortto integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Historical data migration requires manual setup using custom workflows.
- Complex conditional logic may necessitate JavaScript coding for advanced scenarios.
- Real-time updates depend on the polling frequency configured in your Latenode workflow.