Authenticate requests using your GHL credentials with a standard OAuth 2.0 flow. Keep tokens secure and rotate credentials regularly.
Actionstep must securely store and use the access token for GHL calls, applying least-privilege access for integrations.
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 when a new event is created in Actionstep to automatically create a corresponding calendar in Calendars API.
Actions: POST /calendars/ to create calendars; GET /calendars/ to list; GET /calendars/:calendarId to read; PUT /calendars/:calendarId to update; DELETE /calendars/:calendarId to remove.
POST /calendars/ creates a calendar
name, timeZone, color, externalId
Trigger when Actionstep groups change to reflect updates in GHL calendar groups.
Actions: POST /calendars/groups; PUT /calendars/groups/:groupId; DELETE /calendars/groups/:groupId; PUT /calendars/groups/:groupId/status.
POST /calendars/groups; PUT /calendars/groups/:groupId; DELETE /calendars/groups/:groupId;
groupName, groupSlug, calendarId
Trigger when resource or availability data changes in Actionstep to update GHL resources accordingly.
Actions: GET /calendars/resources/:resourceType; GET /calendars/:calendarId/free-slots
GET /calendars/resources/:resourceType; GET /calendars/:calendarId/free-slots
resourceType, calendarId
Automate event-to-calendar synchronization without writing code.
Centralize calendar management across apps for easier scheduling.
Real-time availability checks to boost meeting coordination.
Key elements: endpoints, groups, and resources. Processes include authentication, data mapping, and event-driven automation.
A specific URL and HTTP method used to access a resource in the GHL Calendars API.
The process of proving identity to access GHL APIs, typically via OAuth 2.0 tokens.
A calendar holds events, schedules, and availability data.
Categories like calendars, groups, and resources used by the API.
When Actionstep creates an event, automatically create a matching calendar in Calendars API with the same name and time zone.
Use GET /calendars/:calendarId/free-slots to surface openings and propose times in Actionstep.
Organize calendars into groups to simplify permissions and synchronization across teams.
Obtain GHL API credentials and securely store them in Actionstep.
Connect calendars, groups, and resources endpoints and map fields between systems.
Run end-to-end tests, verify triggers and actions, then deploy to production.
No-code integrations are available to get you started quickly. You can set up triggers and actions in a few clicks to connect Actionstep events to calendar creation. If more customization is needed, you can extend the workflow with additional endpoints. The goal is to enable seamless automation without heavy coding. Two paragraphs here to ensure readability and practical guidance for first-time users.
GHL Calendars API uses OAuth 2.0 tokens for secure access. You will register your app, obtain client credentials, and exchange codes for access tokens. Store tokens securely and refresh them as needed. If you already have an API key setup, follow the recommended credential rotation policy and apply scopes for calendars.write where appropriate.
Yes, you can leverage the free-slots endpoint to surface availability before scheduling in Actionstep. Real-time syncing depends on the frequency of token refresh and the webhook configuration. Start with periodic polling and then migrate to event-driven updates if webhooks are supported.
Typical mappings include: calendar name -> event title, time zone -> event time, calendar color -> category label, and externalId to connect records across systems. You may also map resource types to specific endpoints for granular control.
Test with a sandbox environment. Validate authentication, perform CRUD operations on calendars and groups, and verify that triggers create or update records as expected. Use sample data to simulate real workflows before going live.
Webhook support may vary by plan. If available, configure webhooks to notify you of changes in calendars, groups, or resources and trigger corresponding actions in Actionstep. If not, implement a polling strategy for updates.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
