Authenticate using your GHL credentials to securely access calendars, groups and resources via the Calendars API.
Connect the Zapier App Connector to authorize actions against Calendars API with OAuth or API Key depending on configuration.
POST /calendars/ PUT /calendars/:calendarId DELETE /calendars/:calendarId calendars.readonly GET /calendars/ GET /calendars/:calendarId GET /calendars/:calendarId/free-slots calendars/groups.readonly GET /calendars/groups calendars/groups.write POST /calendars/groups POST /calendars/groups/validate-slug DELETE /calendars/groups/:groupId PUT /calendars/groups/:groupId PUT /calendars/groups/:groupId/status calendars/resources.readonly GET /calendars/resources/:resourceType
Trigger: When a new calendar is created or an existing calendar is updated, sync the change to connected apps.
Actions: Create calendars, update details, or remove calendars as needed via the endpoints.
POST /calendars/; PUT /calendars/:calendarId
calendarName, timeZone, color, calendarId
Trigger: Group creation, updates or deletion to organize calendars.
Actions: Create, update, delete groups; validate slug; assign calendars to groups as needed.
POST /calendars/groups; DELETE /calendars/groups/:groupId; PUT /calendars/groups/:groupId; PUT /calendars/groups/:groupId/status; POST /calendars/groups/validate-slug
groupName, slug, description, calendarIds
Trigger: Retrieve resource types and availability to schedule slots across calendars.
Actions: Readonly access to resource types; fetch specific resources by type.
GET /calendars/resources/:resourceType
Automate calendar workflows across apps without writing code.
View real time availability and slots to prevent double bookings and optimize scheduling.
Centralized control with granular permissions and audit trails for calendar data.
This glossary defines core terms and processes used when integrating the Calendars API with GHL and the Zapier App Connector.
An API is a set of rules and protocols that allows software to communicate and exchange data securely.
OAuth 2.0 is an authorization framework that enables secure access with tokens and scopes.
A slug is a URL friendly identifier used to reference a resource or group in an API call.
Availability describes the open time slots where bookings can occur and be synchronized.
Use the endpoints to automatically create calendars and sync slots when events are booked across apps.
Sync calendar groups automatically based on slug changes to keep teams aligned.
Build dashboards showing resource types and availability across calendars for managers.
Obtain OAuth tokens or API keys and securely store them in your Zapier app.
Choose calendars endpoints, align fields, and configure triggers and actions.
Run tests, verify data flow, and deploy to production.
The Calendars API exposes endpoints for calendars, groups and resources. You can POST to create, GET to read, PUT to update, and DELETE to remove calendars and groups. Use calendars.readonly where you only need read access. Two sample reads help you confirm data structure and ensure mappings align with your workflow. For write operations, use calendars.write and ensure your integration has the proper permissions. Start with a test calendar and a small set of fields to verify correct mapping before scaling to production.
To authenticate, configure OAuth 2.0 or API key methods as supported by your GHL account. Obtain a valid access token with the calendars scope and securely store it in your Zapier app. Refresh tokens before expiry and handle token renewal transparently to avoid interruptions. Maintain least-privilege access by assigning calendars.write only to integrations that truly require write permissions, and use calendars.readonly for read-only integrations.
Yes. You can read and read-write calendars and groups via the endpoints. The calendars.readonly scope allows only reading, while calendars.write enables creating, updating, and deleting calendars and groups. Always test with sandbox data before moving to live data.
In many cases you can build this integration with no code using the Zapier App Connector. Some minimal field mapping and trigger configuration may be required. If complex transformations are needed, you can add small code steps or use built-in transformers.
Rate limits vary by API plan and endpoint. Plan for retries with exponential backoff and implement graceful error handling. Monitor quota usage in the GHL developer console and adjust the sync cadence accordingly.
Map calendar fields to triggers and actions by aligning calendarName, timeZone, color, and slug to the corresponding app fields. Validate your mappings with test events and adjust field types if necessary. Use sample data to verify end-to-end flow.
calendars.readonly provides read access to calendars and groups. calendars.write grants read and write access, including create, update, and delete operations. Distinguish between endpoints that require write permission and those that are safe to expose publicly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
