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


Acuity Scheduling
âš™

Google Cloud Pub\Sub


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

Google Cloud Pub\Sub
Trigger on Webhook
âš™

Acuity Scheduling
âš™
âš™
Iterator
âš™
Webhook response


Save and Activate the Scenario
After configuring Acuity Scheduling, Google Cloud Pub\Sub, 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 Google Cloud Pub\Sub integration works as expected. Depending on your setup, data should flow between Acuity Scheduling and Google Cloud Pub\Sub (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 Google Cloud Pub\Sub
Acuity Scheduling + Twilio: When a new appointment is created in Acuity Scheduling, send an SMS message via Twilio to remind the client about their upcoming appointment.
Acuity Scheduling + Google Sheets: When a new appointment is created in Acuity Scheduling, log the appointment details in a new row of a Google Sheet for tracking and analysis.
Acuity Scheduling and Google Cloud Pub\Sub 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 Google Cloud Pub\Sub
undefined
Similar apps
Related categories
See how Latenode works
FAQ Acuity Scheduling and Google Cloud Pub\Sub
How can I connect my Acuity Scheduling account to Google Cloud Pub\Sub using Latenode?
To connect your Acuity Scheduling account to Google Cloud Pub\Sub 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 Google Cloud Pub\Sub accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send new appointments to Pub/Sub?
Yes, you can! Latenode lets you instantly forward appointment data from Acuity Scheduling to Google Cloud Pub/Sub for real-time processing, using no-code or adding custom logic via JavaScript.
What types of tasks can I perform by integrating Acuity Scheduling with Google Cloud Pub\Sub?
Integrating Acuity Scheduling with Google Cloud Pub\Sub allows you to perform various tasks, including:
- Sending appointment notifications to subscribers for immediate processing.
- Creating real-time dashboards using appointment data from Acuity Scheduling.
- Triggering automated workflows based on appointment events.
- Building advanced analytics pipelines to analyze scheduling trends.
- Storing appointment data securely and efficiently for future access.
Can I filter appointment types before sending to Pub/Sub?
Yes, using Latenode’s visual editor, you can filter specific appointment types from Acuity Scheduling before sending data to Google Cloud Pub/Sub.
Are there any limitations to the Acuity Scheduling and Google Cloud Pub\Sub integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Initial setup requires basic understanding of Google Cloud Pub/Sub topics and subscriptions.
- Large volumes of appointment data may require optimization of your Pub/Sub configuration.
- Complex data transformations might necessitate JavaScript coding within Latenode.