Authorize access to the Calendars API from your GHL account by configuring API keys or OAuth scopes, ensuring secure read/write permissions for calendar data.
In Zapier, connect the Calendars API integration by authenticating with your GHL API name and granting the required permissions for calendar operations.
POST /calendars/ – Create a calendar; PUT /calendars/:calendarId – Update a calendar; DELETE /calendars/:calendarId – Delete a calendar; calendars.readonly – Read calendars (no writes); GET /calendars/ – List calendars; GET /calendars/:calendarId – Get details of a calendar; GET /calendars/:calendarId/free-slots – Check available slots; calendars/groups.readonly – Read calendar groups; GET /calendars/groups – List groups; calendars/groups.write – Create/update groups; POST /calendars/groups – Create a group; POST /calendars/groups/validate-slug – Validate a slug; DELETE /calendars/groups/:groupId – Delete a group; PUT /calendars/groups/:groupId – Update a group; PUT /calendars/groups/:groupId/status – Change group status; calendars/resources.readonly – Read calendar resources; GET /calendars/resources/:resourceType – List resources
Trigger when a new calendar is created or updated in GHL, then push the data to Zapier to trigger downstream actions in your apps.
Actions include create, update, or delete calendars; fetch free slots; assign calendars to groups; and sync metadata.
Example: POST /calendars/ to create; PUT /calendars/:calendarId to update; DELETE /calendars/:calendarId to remove.
Key fields to map: calendarName, timeZone, color, capacity, locale
Trigger on changes to calendar availability or slot status to keep all connected apps in sync.
Actions include reading available slots, blocking slots, and updating slot information across platforms.
Example: GET /calendars/:calendarId/free-slots to check availability.
Key fields: calendarId, slotStart, slotEnd, isAvailable
Trigger when a group is created or updated to propagate changes to related calendars.
Actions include create/update/delete groups and assign calendars to groups.
Example: PUT /calendars/groups/:groupId to update a group; POST /calendars/groups to create a new group.
Key fields: groupName, groupSlug, memberPermissions
Build end-to-end calendar automation without writing code, using triggers and actions across apps.
Connect multiple tools (e.g., Acuity Scheduling, CRM, email) to calendars with minimal setup time.
Maintain real-time calendar availability and bookings across your stack for better scheduling outcomes.
Understand how endpoints, authentication, and data mappings work together to enable calendar automation between Acuity Scheduling and GHL via the Calendars API and Zapier App Connector.
A specific URL in the Calendars API that performs a defined action (e.g., create or read a calendar).
The process of granting an app permission to access GHL data via keys or OAuth scopes.
A collection of scheduled events and availability data used to manage bookings.
The part of the URL that identifies the resource and action in an API request.
Automatically create calendar events in GHL when a new appointment is booked in Acuity Scheduling, and update member data across apps.
Push attendee changes from Acuity to GHL calendars and vice versa to keep everyone in sync.
Trigger reminder emails or messages in other apps when calendar events are created or updated.
Connect your GHL Calendars API and Zapier App Connector using OAuth or API keys to secure access.
Map calendar fields to your apps, set up triggers for new calendars and slots, and define actions.
Create a Zap that chains triggers and actions across Acuity Scheduling, Calendars API, and your CRM or email tool.
Yes. The Calendars API allows reading calendar data, including availability and events. You can fetch calendar lists, details, and resource information to display in your apps. Authentication controls read access to protect sensitive data. For read-heavy workflows, calendars.readonly is sufficient. For full lifecycle management, use the write-enabled endpoints. In beacons of automation, read access often precedes write permissions as you build confidence in the data flow.
Absolutely. You can create, update, and delete calendars and groups via the endpoints listed. In Zapier, configure triggers for creation or updates and actions to reflect those changes across connected apps. Start with calendars/ endpoints to set up calendars, then extend to groups and resources as your workflow grows.
You don’t need to write code to use these endpoints. Zapier App Connector enables no-code automation by connecting triggers and actions to the Calendars API. For advanced scenarios, you can add custom filters or multi-step Zaps to model complex logic.
API credentials are generated from your GHL developer settings or OAuth configuration. In most setups, you’ll create an application in GHL, obtain client credentials, and authorize access to calendars data. Store credentials securely and rotate them as recommended by your security policy.
calendars.readonly allows viewing calendars without the ability to modify data, while calendars.write enables creating, updating, and deleting calendars and related resources. Choose the appropriate scope for your automation needs to balance functionality and security.
Access tokens or OAuth tokens can expire. Use refresh tokens where available, or re-authenticate in Zapier to obtain a new access token. Build your Zap with a re-auth step to minimize downtime in automated workflows.
The free-slots endpoint (GET /calendars/:calendarId/free-slots) is central for availability. Combine it with create/update calendar actions to build responsive booking experiences. Use the groups and resources endpoints to organize calendars and optimize scheduling across teams.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
