How to connect Omnisend and Acuity Scheduling
Create a New Scenario to Connect Omnisend and Acuity Scheduling
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 Omnisend, triggered by another scenario, or executed manually (for testing purposes). In most cases, Omnisend or Acuity Scheduling will be your first step. To do this, click "Choose an app," find Omnisend or Acuity Scheduling, and select the appropriate trigger to start the scenario.

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

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

Omnisend
⚙

Acuity Scheduling

Authenticate Acuity Scheduling
Now, click the Acuity Scheduling node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Acuity Scheduling settings. Authentication allows you to use Acuity Scheduling through Latenode.
Configure the Omnisend and Acuity Scheduling 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 Omnisend and Acuity Scheduling 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
⚙

Acuity Scheduling
Trigger on Webhook
⚙
Omnisend
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Omnisend, Acuity Scheduling, 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 Omnisend and Acuity Scheduling integration works as expected. Depending on your setup, data should flow between Omnisend and Acuity Scheduling (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Omnisend and Acuity Scheduling
Acuity Scheduling + Omnisend + Zoom: When a new appointment is booked in Acuity Scheduling, create or update a contact in Omnisend, then create a Zoom meeting and update the Omnisend contact with the Zoom meeting link.
Acuity Scheduling + Google Sheets + Omnisend: When a new appointment is created in Acuity Scheduling, add a new row to a Google Sheet with the appointment details. Then, send a custom event to Omnisend to track the new appointment.
Omnisend and Acuity Scheduling integration alternatives
About Omnisend
Use Omnisend in Latenode to automate email & SMS marketing based on real-time data. Connect e-commerce platforms and CRMs, then trigger personalized campaigns. Stop overspending on rigid marketing tools. Latenode's visual editor and flexible logic create scalable automation at a fraction of the cost.
Related categories

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
See how Latenode works
FAQ Omnisend and Acuity Scheduling
How can I connect my Omnisend account to Acuity Scheduling using Latenode?
To connect your Omnisend account to Acuity Scheduling on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Omnisend and click on "Connect".
- Authenticate your Omnisend and Acuity Scheduling accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger Omnisend campaigns on new appointments?
Yes, with Latenode, triggering Omnisend campaigns upon new Acuity Scheduling appointments is easy. Automate personalized messages and boost engagement using our visual editor and advanced logic.
What types of tasks can I perform by integrating Omnisend with Acuity Scheduling?
Integrating Omnisend with Acuity Scheduling allows you to perform various tasks, including:
- Send personalized welcome emails via Omnisend after booking an appointment.
- Update contact properties in Omnisend based on appointment types.
- Trigger abandoned cart emails in Omnisend for incomplete bookings.
- Send SMS reminders via Omnisend before scheduled appointments.
- Segment Omnisend contacts based on their appointment history.
Can I use JavaScript to transform data between Omnisend and Acuity Scheduling?
Yes, Latenode allows you to use JavaScript code blocks for complex data transformations, offering unmatched flexibility between Omnisend and Acuity Scheduling.
Are there any limitations to the Omnisend and Acuity Scheduling integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations might require JavaScript knowledge.
- Real-time synchronization depends on the API rate limits of both services.
- Custom field mappings may require initial setup and testing.