Calendars API uses OAuth 2.0 with the calendars.write scope to control access. Obtain an access token from your GHL developer console and pass it in your API requests.
In Zapier App Connector, configure OAuth 2.0 for the Calendars API connection. Zapier will manage token refresh and securely store credentials so your workflows stay online.
Key endpoints include POST /calendars/ to create calendars, PUT /calendars/:calendarId to update, DELETE /calendars/:calendarId to remove, calendars.readonly for read-only access, GET /calendars/ and GET /calendars/:calendarId for retrieval, GET /calendars/:calendarId/free-slots for availability, calendars.groups.readonly and GET /calendars/groups for groups, POST /calendars/groups and POST /calendars/groups/validate-slug for group creation and validation, DELETE /calendars/groups/:groupId and PUT /calendars/groups/:groupId for updates, PUT /calendars/groups/:groupId/status to change status, calendars/resources.readonly and GET /calendars/resources/:resourceType for resources.
Trigger: a new form submission in APPNAME; Action: POST /calendars/ to create a calendar in Calendars API.
Actions: POST /calendars/ to create; PUT /calendars/:calendarId to update; GET /calendars/ to list calendars.
POST /calendars/
Required: name, timezone; Optional: color, description, location
Trigger: a calendar is updated in APPNAME; Action: PUT /calendars/:calendarId
Actions: PUT /calendars/:calendarId to apply changes; optionally PUT /calendars/groups/:groupId for group adjustments.
PUT /calendars/:calendarId
calendarId, payload with updated fields (name, timezone, color)
Trigger: new group in APPNAME; Action: POST /calendars/groups and POST /calendars/groups/validate-slug
Actions: POST /calendars/groups; PUT /calendars/groups/:groupId; PUT /calendars/groups/:groupId/status
POST /calendars/groups
group name, slug, description
No coding required—build powerful calendar automations with a visual workflow designer in Zapier.
Rapid setup and deployment reduce time to value and enable rapid testing.
Secure token management and centralized access controls scale with your team.
This glossary defines API, endpoint, trigger, action, payload, authentication, scope, and rate limits in the context of the Calendars API and the Zapier App Connector.
A set of endpoints that let apps read, create, update, and delete calendar data.
The authorization framework used to obtain access tokens for API requests.
A specific URL that performs a defined calendar operation, such as POST /calendars/.
The data you send with API requests to create or update resources, typically in JSON.
When a user submits a form in APPNAME, automatically create a calendar in Calendars API with the form data using POST /calendars/.
Push free-slots data from GET /calendars/:calendarId/free-slots into scheduling widgets in real time.
Automate the creation and management of calendar groups with POST /calendars/groups and status updates with PUT /calendars/groups/:groupId/status.
Create a new connection in Zapier App Connector and authorize access to Calendars API using OAuth 2.0.
Define exactly how your APPNAME data maps to Calendars API endpoints for creation, updates, and reads.
Run tests end-to-end, verify payloads and token validity, then deploy to production.
Calendars API is a RESTful interface that lets you create, read, update, and delete calendars and related resources. It exposes endpoints for calendars, groups, and resources that you can call from Zapier App Connector to automate scheduling workflows. This no-code approach enables you to build calendar-driven automations without developing a custom backend. This integration enables no-code automation between Zapier App Connector and the GHL Calendars API, letting you automate calendar creation, updates, and availability without writing code.
Scopes determine what your app can do; calendars.write allows creating and updating calendars, while calendars.readonly accesses read operations. You should request only the minimum scope required for your workflow and obtain user consent. The exact scopes can be adjusted based on the endpoints you need (read vs write).
Authentication is handled via OAuth 2.0. You obtain an access token in the GHL developer console and configure Zapier App Connector to use it for API calls. Zapier will manage token refresh so your workflows stay connected without manual re-auth. Ensure the token has the calendars.write scope for create/update operations.
Yes. You can create and manage calendar groups with endpoints under /calendars/groups, including validation (/validate-slug) and status updates (/groups/:groupId/status). Endpoints also support read-only access for groups for reporting and auditing. This enables complex group-based calendar management without code.
The integration exposes endpoints for calendars, groups, and resources. Key actions include create, read, update, delete calendars, manage groups, and fetch resources. Visit the Endpoints section for a complete list of available endpoints and their required fields.
No coding is required to start. Zapier App Connector provides a visual builder to connect APPNAME data to Calendars API. If you need more advanced transformations, you can insert lightweight code steps or use built-in field mappings.
Common auth errors usually indicate expired tokens or invalid scopes. Re-authenticate the connection and ensure the correct endpoints and tokens are used. Check your OAuth setup, verify the access token, and confirm the calendars.write scope is granted.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
