Obtain a GHL API key with calendars.write scope and securely store it in Acumbamail to enable data exchange.
Configure Acumbamail to accept incoming API requests from GHL or display a secure integration key to authorize access.
Key endpoints include: POST /calendars/ (create); GET /calendars/ (list); GET /calendars/:calendarId (retrieve); PUT /calendars/:calendarId (update); DELETE /calendars/:calendarId (delete); GET /calendars/:calendarId/free-slots (check availability); GET /calendars (list including groups); GET /calendars/groups; POST /calendars/groups; POST /calendars/groups/validate-slug; PUT /calendars/groups/:groupId; DELETE /calendars/groups/:groupId.
Trigger: A new calendar is created in Acumbamail, which creates a calendar via POST /calendars/ in GHL.
Actions: POST /calendars/; PUT /calendars/:calendarId; GET /calendars/.
Key endpoints used: POST /calendars/, PUT /calendars/:calendarId, GET /calendars/.
Essential fields: name, time_zone, color, accountId.
Trigger: When a group is created in Acumbamail, use POST /calendars/groups to create a corresponding group.
Actions: POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId
Endpoints: GET /calendars/groups, POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, POST /calendars/groups/validate-slug
Key fields: slug, name, status
Trigger: A request for free slots is made, retrieve via GET /calendars/:calendarId/free-slots.
Actions: GET /calendars/:calendarId/free-slots
Endpoints: GET /calendars/:calendarId/free-slots
Key fields: resourceType, duration, timezone
No-code automation: build workflows without writing code.
Rapid integration: connect your calendar data to campaigns with a few clicks.
Scalable calendar management across teams.
Understand endpoints, triggers, actions, and data fields used to connect Calendars API with Acumbamail.
A URL that performs a specific operation on the Calendars API.
Methods used to verify identity and authorize access between GHL and Acumbamail.
A callback URL that receives events from the Calendars API.
A data object such as calendars, groups, or slots within the API.
Trigger Acumbamail campaigns when a calendar event is created or updated.
Use calendar free-slots data to time your campaigns optimally.
Assign calendars to campaigns and coordinate team calendars automatically.
Generate a GHL API key with the calendars.write scope and securely store it in Acumbamail.
Add the API key to Acumbamail and authorize integration.
Run test operations to confirm calendars data flows between GHL and Acumbamail.
The Calendars API requires the calendars.write scope to create and modify calendars, and read-only access to list and view calendars. Always scope minimally and rotate keys; use secure storage.
Yes, you can read calendars via GET /calendars and GET /calendars/:calendarId without requiring write access. Write access is only required if you need to create or modify calendars.
In Acumbamail, initiate OAuth or API key sharing; then authorize the GHL app to access calendars. Use the provided credentials in the GHL integration settings to complete the connection.
Key endpoints include creating calendars, listing calendars, updating, deleting, and retrieving free-slots. See the endpoint list in the integration docs for full details.
Zapier can be used as an optional bridge, but direct GHL to Calendars API connections can work without it. If you prefer Zapier for automation, map triggers and actions to GHL events accordingly.
Rate limits depend on your GHL plan; monitor headers to adjust request frequency. Implement caching and batching where possible to minimize calls.
The data flow includes calendars, groups, and slots; fields include name, slug, time_zone, and status. If you customize fields, ensure mapping aligns with both GHL and Acumbamail schemas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
