Use OAuth 2.0 with the calendars.write and calendars.readonly scopes to securely access calendars data.
Authenticate in Zapier using OAuth or API key and authorize access to calendars resources in GHL.
POST /calendars/ creates a calendar; PUT /calendars/:calendarId updates a calendar; DELETE /calendars/:calendarId removes a calendar; GET /calendars/ lists calendars; GET /calendars/:calendarId retrieves a calendar; GET /calendars/:calendarId/free-slots checks availability; GET /calendars/groups reads groups; POST /calendars/groups creates a group; POST /calendars/groups/validate-slug validates a group slug; DELETE /calendars/groups/:groupId removes a group; PUT /calendars/groups/:groupId updates a group; PUT /calendars/groups/:groupId/status changes group status; calendars/resources.readonly lists resources; GET /calendars/resources/:resourceType retrieves resources.
Trigger: New calendar is created in Calendars API
Actions: Create calendar in GHL with Zapier, update fields, assign resources
Methods: POST /calendars/ and PUT /calendars/:calendarId
Key fields: id, name, timeZone, color, ownerId
Trigger: Calendar updated in source system
Actions: Update in Calendars API; reflect changes in related events
Methods: PUT /calendars/:calendarId; GET /calendars/:calendarId
Key fields: calendarId, status, syncFlag
Trigger: Availability check requested
Actions: Retrieve free-slots via GET /calendars/:calendarId/free-slots and schedule
Methods: GET /calendars/:calendarId/free-slots
Key fields: calendarId, startTime, endTime, duration
Visual workflow builder lets you automate calendars without writing code
Instant automation between Calendars API and your favorite apps
Scalable automation with auditable logs and retries
Core terms and how they relate to Calendars API and the Zapier App Connector including calendars, events, endpoints, OAuth and slug validation.
A calendar is a collection of events and availability identified by calendarId.
An individual appointment or entry within a calendar with a start and end time.
An API route that performs a specific function such as create read update or delete.
OAuth 2.0 is the standard authorization protocol used to grant scoped access.
Automatically create calendar events in Calendars API when a deal lands on scheduled in your CRM via Zapier
Publish free-slots to scheduling pages and chat apps to reduce back-and-forth
Create multiple calendars from templates and assign resources automatically in bulk
In Zapier authorize the Calendars API connection and select calendars.write
Choose a trigger such as New Calendar and map actions to create update or fetch calendars
Run a test to verify data flow and then enable the connection
The calendars.write scope lets you create and modify calendars and associated events. It enables automation of scheduling tasks in GHL and connected apps via Zapier. Respect permissions and rate limits.
Authenticate in GHL using OAuth 2.0 for the calendars API and then connect the Zapier App Connector with a secure OAuth flow. Map the connection once approved to access calendar data.
Endpoints include creating updating retrieving and deleting calendars and managing groups and resources. Use GET POST PUT and DELETE as appropriate.
Yes you can check availability using the free-slots endpoint. Pass the calendarId and time window to retrieve open slots for scheduling.
No heavy coding is required. The Zapier App Connector provides a no-code interface to wire triggers actions and searches against the Calendars API.
Respect API rate limits implement retries and handle errors with meaningful messages. Use built in Zapier tooling for backoff and logging.
Webhook support and logs are available in the Zapier connector and in GHL developer docs. Enable logs to troubleshoot data flow.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
