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

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

OpenPhone
Configure the OpenPhone
Click on the OpenPhone node to configure it. You can modify the OpenPhone 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 OpenPhone node, select Acuity Scheduling from the list of available apps, and choose the action you need from the list of nodes within Acuity Scheduling.

OpenPhone
⚙

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 OpenPhone 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 OpenPhone 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
⚙
OpenPhone
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring OpenPhone, 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 OpenPhone and Acuity Scheduling integration works as expected. Depending on your setup, data should flow between OpenPhone 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 OpenPhone and Acuity Scheduling
Acuity Scheduling + Google Calendar + OpenPhone: When a new appointment is booked in Acuity Scheduling, an event is created in Google Calendar. OpenPhone then logs the details of the call to the Google Calendar event.
Acuity Scheduling + Zoom + OpenPhone: When a new appointment is created in Acuity Scheduling, a Zoom meeting is created. OpenPhone then sends the Zoom meeting link via SMS to the person who booked the appointment.
OpenPhone and Acuity Scheduling integration alternatives
About OpenPhone
Use OpenPhone in Latenode to automate SMS and call workflows. Log activities, trigger actions based on call outcomes, and sync data to CRMs. By using Latenode, you orchestrate OpenPhone within complex workflows, adding logic and integrations not available in OpenPhone alone. Scale customer communication using no-code tools and AI.
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 OpenPhone and Acuity Scheduling
How can I connect my OpenPhone account to Acuity Scheduling using Latenode?
To connect your OpenPhone account to Acuity Scheduling on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select OpenPhone and click on "Connect".
- Authenticate your OpenPhone and Acuity Scheduling accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send SMS reminders for upcoming appointments?
Yes, you can! Latenode allows you to automatically send SMS reminders via OpenPhone for Acuity Scheduling appointments, reducing no-shows and improving customer communication.
What types of tasks can I perform by integrating OpenPhone with Acuity Scheduling?
Integrating OpenPhone with Acuity Scheduling allows you to perform various tasks, including:
- Send a personalized SMS when a new appointment is scheduled.
- Automatically call clients before an appointment for confirmation.
- Create OpenPhone contacts from new Acuity Scheduling clients.
- Log appointment details in OpenPhone call history.
- Send follow-up SMS messages after completed appointments.
How do I handle errors in my OpenPhone Latenode flows?
Latenode provides robust error handling. Use conditional logic and error-handling blocks to manage failures and send notifications, ensuring flow stability.
Are there any limitations to the OpenPhone and Acuity Scheduling integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex conditional logic may require JavaScript coding.
- Real-time data synchronization depends on API availability.
- High-volume SMS sending might be subject to OpenPhone limits.