To start, grant OAuth permissions to allow Zapier App Connector to access your Calendars data in Calendars API. This ensures secure, token-based access.
Approve the app to act on your Calendars data within your Calendars API account.
POST /calendars/ — Create a calendar; PUT /calendars/:calendarId — Update a calendar; DELETE /calendars/:calendarId — Delete a calendar; GET /calendars/ — List calendars; GET /calendars/:calendarId — Retrieve a calendar; GET /calendars/:calendarId/free-slots — Get available slots; GET /calendars/groups — List 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 — Update group status; GET /calendars/resources/:resourceType — List resources.
Trigger: When a new calendar is created or updated in Calendars API
Actions: Create, update, delete calendars; list calendars; read calendar details
POST /calendars/
calendarName, timezone, locale, color
Trigger: Availability updates or on-demand slot sync
Actions: Get calendars; fetch free slots; push slot updates to Accelevents
GET /calendars/:calendarId/free-slots
calendarId, dateRange, duration
Trigger: Groups or permissions are updated
Actions: Create, update, delete groups; adjust group status
POST /calendars/groups; PUT /calendars/groups/:groupId; DELETE /calendars/groups/:groupId; PUT /calendars/groups/:groupId/status
groupName, slug, status, permissions
Automate calendar workflows without writing code.
Keep calendars, events, and slots in sync across systems using ready-made Zap templates.
Speed up onboarding with drag-and-drop automations and built-in error handling.
This glossary covers endpoints, authentication, triggers, actions, and data mappings used to connect Calendars API with Zapier App Connector.
A URL path and HTTP method used to access or modify a resource in the API.
The process of granting access via OAuth tokens or API keys to securely call the API.
An event in Calendars API that starts a Zapier workflow.
An operation executed in response to a trigger, such as creating or updating a calendar.
Whenever a new event is added in Accelevents, automatically create a matching calendar in Calendars API via Zapier.
Keep available slots in Calendars API up-to-date in Accelevents to prevent double bookings.
Control who can view or modify calendars by groups defined in Calendars API.
Grant access to Calendars API from Zapier to establish a secure connection.
Select and align fields such as calendarName, timezone, and color attributes.
Create multi-step automations that coordinate calendars with events in Accelevents.
To connect, create the Zapier App Connector connection and authorize access to Calendars API in your GHL account. Then configure the trigger and actions to align with your calendars workflow. Use test mode to verify each step before going live.
The integration uses OAuth 2.0 tokens to authorize access. In some setups you may also use API keys for service-to-service calls; store credentials securely and rotate them regularly.
You have access to standard endpoints such as create, read, update, and delete calendars and groups. For slots, use the free-slots endpoint to retrieve availability. Test calls in a sandbox to confirm behavior.
In Zapier, map each trigger field to the corresponding API field. Example: calendarName maps to the calendar name field; calendarId maps to the target calendar; dateRange to time window for slots.
Use Zapier’s built-in test tools and sample data. Run end-to-end tests that create a calendar, schedule an event, and pull slots to verify data flows and error handling. Check task history for diagnostics.
Yes. You can manage calendar groups via the calendars/groups endpoints to control who can view or modify calendars. Assign users to groups and apply permissions accordingly.
If an API call fails, rely on Zapier retries and exponential backoff. Monitor error messages, implement idempotent actions where possible, and respect API rate limits.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
