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


Acuity Scheduling
⚙

MySQL


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

MySQL
Trigger on Webhook
⚙

Acuity Scheduling
⚙
⚙
Iterator
⚙
Webhook response


Save and Activate the Scenario
After configuring Acuity Scheduling, MySQL, 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 MySQL integration works as expected. Depending on your setup, data should flow between Acuity Scheduling and MySQL (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 MySQL
Acuity Scheduling + MySQL + Slack: When a new appointment is booked in Acuity Scheduling, the appointment data is saved to a MySQL database. Subsequently, a notification is sent to a specified Slack channel to inform the team about the new booking.
Acuity Scheduling + MySQL + Google Sheets: When an appointment is canceled in Acuity Scheduling, the cancellation is tracked in a MySQL database by updating the corresponding row. The changes are then logged in a Google Sheet for auditing and reporting purposes.
Acuity Scheduling and MySQL 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 MySQL
Use MySQL in Latenode to automate database tasks. Read, update, or create records based on triggers from other apps. Streamline data entry, reporting, or inventory management. Latenode's visual editor simplifies MySQL integrations, allowing you to build scalable workflows with no-code tools or custom JavaScript logic.
Similar apps
Related categories
See how Latenode works
FAQ Acuity Scheduling and MySQL
How can I connect my Acuity Scheduling account to MySQL using Latenode?
To connect your Acuity Scheduling account to MySQL 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 MySQL accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically back up appointment data to MySQL?
Yes, you can! With Latenode, automate backups and ensure data safety. Schedule regular data transfers to MySQL, safeguarding your Acuity Scheduling information with ease and reliability.
What types of tasks can I perform by integrating Acuity Scheduling with MySQL?
Integrating Acuity Scheduling with MySQL allows you to perform various tasks, including:
- Sync new appointment data to a MySQL database in real time.
- Create custom reports using combined Acuity Scheduling and MySQL data.
- Trigger automated notifications based on appointment updates.
- Update customer information in MySQL when appointments are scheduled.
- Archive historical appointment data for long-term analysis.
How secure is my Acuity Scheduling data when using Latenode?
Latenode employs robust security measures, including encryption and secure authentication protocols, ensuring your data remains safe. Data privacy is our top priority.
Are there any limitations to the Acuity Scheduling and MySQL integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Large data transfers may take time to process depending on server load.
- Custom SQL queries beyond basic CRUD operations require JavaScript knowledge.
- Complex workflows with many steps might require more server resources.