How to connect Acuity Scheduling and RingCentral
Create a New Scenario to Connect Acuity Scheduling and RingCentral
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 RingCentral will be your first step. To do this, click "Choose an app," find Acuity Scheduling or RingCentral, 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 RingCentral Node
Next, click the plus (+) icon on the Acuity Scheduling node, select RingCentral from the list of available apps, and choose the action you need from the list of nodes within RingCentral.


Acuity Scheduling
⚙

RingCentral


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

RingCentral
Trigger on Webhook
⚙

Acuity Scheduling
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Acuity Scheduling, RingCentral, 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 RingCentral integration works as expected. Depending on your setup, data should flow between Acuity Scheduling and RingCentral (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 RingCentral
Acuity Scheduling + RingCentral + Google Calendar: When a new appointment is booked in Acuity Scheduling, a RingCentral meeting bridge is created and the details are added as an event in Google Calendar.
RingCentral + Acuity Scheduling + Slack: When a new missed call is registered in RingCentral, a Slack notification is sent, prompting the user to book a follow-up appointment in Acuity Scheduling.
Acuity Scheduling and RingCentral 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 RingCentral
Integrate RingCentral with Latenode to automate call logging, SMS alerts, and contact management. Trigger workflows based on call events, automatically updating records in other apps like CRMs or support tools. Use Latenode's visual editor and scripting nodes for customized call handling and data synchronization.
Similar apps
Related categories
See how Latenode works
FAQ Acuity Scheduling and RingCentral
How can I connect my Acuity Scheduling account to RingCentral using Latenode?
To connect your Acuity Scheduling account to RingCentral 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 RingCentral accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send RingCentral SMS appointment reminders from Acuity Scheduling?
Yes, you can! Latenode lets you automatically send SMS reminders via RingCentral based on Acuity Scheduling appointments. Reduce no-shows with timely, automated notifications.
What types of tasks can I perform by integrating Acuity Scheduling with RingCentral?
Integrating Acuity Scheduling with RingCentral allows you to perform various tasks, including:
- Send RingCentral SMS messages when a new appointment is booked.
- Create RingCentral meetings automatically for new Acuity Scheduling appointments.
- Update RingCentral contacts when appointment details change in Acuity Scheduling.
- Log completed appointments in RingCentral as call activities.
- Trigger RingCentral notifications for appointment cancellations.
What Acuity Scheduling data can I access within Latenode workflows?
Latenode provides access to appointment details, client information, appointment types, and scheduling configurations for dynamic automation.
Are there any limitations to the Acuity Scheduling and RingCentral integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex workflows may require JavaScript knowledge.
- Data transfer is subject to API rate limits of both services.
- Real-time synchronization depends on the polling interval.