To begin, generate credentials for Calendars API in your GHL account. Use OAuth 2.0 or an API key as supported by the platform and store them securely.
Authorize Act! to access Calendars API resources by configuring the connection and granting the required scopes, such as calendars.write.
The Calendars API exposes endpoints to create, read, update, delete calendars, manage groups and resources, and check free slots. Use the endpoints listed below to build your automations in Act!.
Trigger: When a new calendar is needed based on Act! workflows, create it in Calendars API.
Actions: POST /calendars/ to create, PUT /calendars/:calendarId to update, DELETE /calendars/:calendarId to delete.
POST /calendars/, PUT /calendars/:calendarId, DELETE /calendars/:calendarId
Key fields: name, description, color, timeZone, location, metadata
Trigger: When preparing a schedule in Act!, fetch calendar lists or availability data.
Actions: GET /calendars/, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots.
GET /calendars/, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots
Key fields: calendarId, startDate, endDate, timeZone
Trigger: When organizing teams or resources within Act!, sync groups and resources in Calendars API.
Actions: POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, GET /calendars/groups, POST /calendars/groups/validate-slug, PUT /calendars/groups/:groupId/status, GET /calendars/resources/:resourceType.
GET /calendars/groups, POST /calendars/groups, POST /calendars/groups/validate-slug, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status, GET /calendars/resources/:resourceType
Key fields: groupId, slug, name, status, resourceType
Automate calendar provisioning and updates without writing code, using pre-built endpoints.
Keep Act! and calendar data in sync in real time to reduce scheduling conflicts.
Leverage ready-to-use endpoints to build robust scheduling automations quickly.
This glossary defines the core terms used in the Calendars API and Act! integration and describes how data flows between systems.
A URL path that exposes a specific function in the Calendars API.
A calendar resource that groups events and availability.
The method used to verify identity and grant access (OAuth 2.0, API keys).
Open time windows during which events can be scheduled.
Whenever Act! creates or updates an event, automatically mirror it as a calendar in Calendars API to keep events in sync.
Pull available time windows from Calendars API and surface them in Act! workflows to streamline booking.
Organize calendars by groups and resources and push assignments from Act! to calendars automatically.
Obtain OAuth tokens and configure credentials for Calendars API in GHL.
Enable relevant endpoints (calendars, groups, resources) and map fields to Act! data.
Run tests, review logs, and publish your workflow.
You can automate the creation of calendars, updates, and deletions from Act! workflows. This enables teams to mirror events and scheduling structures without manual data entry. For consistency and security, define clear permissions and validation rules for each action within your automation flows.
OAuth 2.0 provides secure, token-based access and granular scopes. API keys offer a simpler option for internal environments. Maintain secret storage and rotate credentials regularly. Always follow the recommended authentication method supported by Calendars API and your GHL setup.
Key endpoints include calendars, calendars/:calendarId, calendars/:calendarId/free-slots, calendars/groups, and calendars/resources/:resourceType. These cover creation, retrieval, updates, deletions, and availability checks. Use the endpoints that align with your workflow needs and map fields accordingly.
Yes. Use GET /calendars/:calendarId/free-slots to fetch open time windows. You can filter by date range and time zone to present actionable options in Act!. Combine with scheduling rules to automate booking based on availability.
Groups organize calendars for teams or departments, while resources represent assets like rooms or equipment. You can create, update, and associate calendars with groups and resources via the provided endpoints. This helps coordinate invites and avoid double-bookings across Act! workflows.
Rate limits apply per API key or OAuth token. Plan your calls to batch requests where possible and use caching for static data like calendar lists. If you hit limits, implement retry logic with backoff and monitor quotas in your GHL dashboard.
Field mappings vary by endpoint, but common mappings include calendar name, ID, time zone, color, and description. Review the endpoint documentation and test mappings in a sandbox environment. If you need help, start with a basic mapping and expand as your flows mature.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
