Use OAuth 2.0 with your GHL credentials to authorize Rankr to access calendars. The required scope is calendars.write (readonly access can be granted if you just need to view calendars).
After authorization, Rankr stores a secure token to access your GHL calendars and will refresh it as needed to maintain a seamless connection.
Primary endpoints include creating, updating, deleting, and fetching calendars, groups, and resources. Examples: POST /calendars/, PUT /calendars/:calendarId, GET /calendars/, POST /calendars/groups, GET /calendars/groups, GET /calendars/resources/:resourceType, and more. Use these to build robust calendar automation between GHL and Rankr.
Trigger: when a calendar is created in Rankr, automatically create a corresponding calendar in GHL via POST /calendars/.
Actions: sync calendar name, slug, timezone, and color; ensure events and availability mirror across both systems.
POST /calendars/
Key fields: name, slug, color, timezone
Trigger: group creation or updates in Rankr propagate to GHL calendar groups, and vice versa.
Actions: create, update, and delete groups using POST /calendars/groups, PUT /calendars/groups/:groupId, and DELETE /calendars/groups/:groupId.
Methods include POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId.
Key fields: group name, slug, status
Trigger: changes to resources in GHL update Rankr calendars, and resource updates in Rankr reflect back in GHL.
Actions: map resourceType to calendars/resources/:resourceType and keep availability synchronized across platforms.
GET /calendars/resources/:resourceType
Key fields: resourceType, capacity, status
Build powerful calendar automations without writing a line of code. Use triggers, actions, and scheduling rules to orchestrate calendars between GHL and Rankr.
Experience real-time synchronization, so changes in one system are reflected instantly in the other.
Centralized calendar governance reduces manual updates and human error across teams.
This glossary defines terms and processes used in the Calendars API integration between GHL and Rankr, including endpoints, triggers, actions, and fields.
GHL refers to the API layer used to manage calendars, groups, and resources within the GHL ecosystem. It enables calendar automation and integration with Rankr.
Rankr is the app that connects to GHL to automate calendar workflows and streamline calendar-related automation.
A specific URL path (for example, POST /calendars/) that performs an action in the Calendars API.
A URL-friendly identifier used for calendars or groups to ensure consistent references across integrations.
Automatically push reminders from Rankr to GHL and connected messaging tools when a calendar event is created or updated.
Use resource types to block time and optimize availability across teams with synchronized calendars.
Grant different teams access to specific calendar groups via GHL for streamlined permissions.
Register the Calendars API in GHL and obtain your client ID and client secret.
Grant Rankr the requested scopes and authorize the connection to access calendars.
Test the integration in a sandbox environment and then move to production.
The Calendars API is the set of endpoints in GHL that lets you create, update, fetch, and delete calendars, calendar groups, and resources. It enables automation of calendar tasks from Rankr without manual data entry. You can trigger workflows based on calendar events and keep all systems in sync. Use this API to drive calendar-backed automations, such as creating calendars from Rankr events or updating calendar details in response to Rankr triggers.
Required permissions include calendars.write for modifying calendars and calendars.readonly for viewing calendars. When you connect Rankr, ensure your OAuth scopes include the write access to enable full automation and syncing. If you only need to read data, readonly access suffices.
Key endpoints for calendar management include POST /calendars/ to create, PUT /calendars/:calendarId to update, GET /calendars/ to list, and GET /calendars/:calendarId for details. For groups, use POST /calendars/groups, PUT /calendars/groups/:groupId, DELETE /calendars/groups/:groupId, and GET /calendars/groups. Resource endpoints include GET /calendars/resources/:resourceType.
Yes. You can synchronize calendar groups and resources between GHL and Rankr. Triggers can propagate group and resource changes across systems, and actions can create, update, or delete entries to maintain consistency.
Connection security is maintained via OAuth 2.0 authorization and token-based access. Data transmitted between Rankr and GHL is protected, and tokens are refreshed automatically as needed. Follow best practices for securely storing client IDs and secrets.
No coding is required to set up the integration. Use the provided triggers and actions in Rankr to map fields, configure endpoints, and automate calendar workflows with a few clicks.
If you need help, consult the Rankr support resources, community guides, or the developer documentation for GHL endpoints. You can reach support via the Rankr help center for setup, troubleshooting, and optimization tips.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
