Authenticate using OAuth 2.0 tokens with the Calendars API scope calendars.write. Store tokens securely and refresh as needed.
Authorize the ActiveTrail app to access Calendars API resources and set up token renewal for uninterrupted automation.
POST /calendars/, PUT /calendars/:calendarId, DELETE /calendars/:calendarId, calendars.readonly, GET /calendars/, GET /calendars/:calendarId, GET /calendars/:calendarId/free-slots, calendars/groups.readonly, GET /calendars/groups, calendars/groups.write, POST /calendars/groups, POST /calendars/groups/validate-slug, DELETE /calendars/groups/:groupId, PUT /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status, calendars/resources.readonly, GET /calendars/resources/:resourceType
Trigger: a new calendar is created in Calendars API.
Actions: push calendar details to ActiveTrail to enable event scheduling and reminders.
POST /calendars/
Key fields: calendarId, name, timeZone
Trigger: update calendar details in Calendars API.
Actions: mirror updated fields to ActiveTrail calendars.
PUT /calendars/:calendarId
Key fields: calendarId, name, description, timeZone
Trigger: retrieve free slots for a calendar.
Actions: use slot data to schedule events in ActiveTrail.
GET /calendars/:calendarId/free-slots
Key fields: calendarId, date, startTime, endTime
No-code automation to create and manage calendars without writing a line of code.
Real-time syncing of calendars keeps teams aligned and events up to date.
Unified calendar management across apps through a single connector.
Key elements include API endpoints, authentication, triggers, actions, and data mapping between Calendars API and ActiveTrail.
A specific URL path and HTTP method used to access a resource in the Calendars API.
The process of granting permission and obtaining access tokens to call API endpoints.
A secure authorization framework that allows apps to access resources on behalf of users without sharing passwords.
An item such as a calendar, group, or slot managed by the Calendars API.
Automatically offer available calendar slots to clients and sync bookings with ActiveTrail campaigns.
Share calendars with teams and automate permissions through the App Connector.
Trigger reminder campaigns in ActiveTrail based on calendar events.
Step 1: In GHL, add Calendars API as a connection and grant access to ActiveTrail.
Step 2: Map endpoints to ActiveTrail actions and set triggers (new calendar, updated calendar, or free slots).
Step 3: Run tests, verify data flow, and enable live automation.
No coding is required for standard calendar tasks when using the App Connector. The setup guides you through authentication, endpoint mapping, and data sync without writing code. If you do want custom workflows, you can extend with additional automation using your favorite no-code tools.
Calendars endpoints cover creating calendars, updating details, reading calendars, and retrieving available slots. Map these to ActiveTrail actions to keep campaigns and events in sync. For robust workflows, combine with groups and resources endpoints.
Authenticate with OAuth 2.0 tokens scoped to calendars.write. Use refresh tokens and store securely. The App Connector guides you through the authorization flow.
Yes. Use the free-slots endpoint to fetch availability and then schedule from ActiveTrail. You can automate slot selection and booking by connecting triggers to campaigns.
Absolutely. The integration is designed for no-code users, with step-by-step setup, visual mapping, and built-in triggers to automate common calendar tasks.
Benefits include faster setup, fewer errors, real-time data sync, and a single connector to manage calendars across apps without custom development.
Endpoints are listed in this guide. You can also view them in the API reference within the App Connector. They cover calendars, groups, and resources.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
