To access Calendars API from Active Knocker, generate an API key in your GHL developer portal and grant the calendars.write scope. Use OAuth tokens where required and keep credentials secure.
Authorize Active Knocker to act on your GHL calendars using OAuth 2.0. When prompted, grant the necessary scopes and store credentials in a secure vault.
Key endpoints include: 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: New lead booked via Active Knocker.
Actions: POST /calendars/ to create an event; optionally POST /calendars/groups to organize; PUT /calendars/:calendarId to update if needed.
POST /calendars/
calendarName, startTime, endTime, attendees, description
Trigger: Availability updated in Active Knocker.
Actions: GET /calendars/:calendarId/free-slots to fetch availability; POST/PUT to create or adjust bookings as needed.
GET /calendars/:calendarId/free-slots
calendarId, userId, date, time, duration
Trigger: Group calendar updated in GHL.
Actions: POST /calendars/groups to create; PUT /calendars/groups/:groupId to update; DELETE /calendars/groups/:groupId to remove.
POST /calendars/groups
groupName, groupId, permissions
Fast automation: configure workflows without writing code.
Real‑time synchronization of events and availability across apps.
Centralized calendar management embedded in your existing workflow.
Key elements include endpoints, triggers, actions, and field mappings. Processes: authenticate, configure endpoints, test, deploy, and monitor performance.
Application Programming Interface that allows Active Knocker to interact with GHL Calendars data.
Standard authorization framework used to grant tokens and secure access to GHL data.
A specific URL path and HTTP method used to perform an action on the GHL Calendars API.
A scheduling block representing events, availability, and bookings in GHL.
When a lead books, automatically create a calendar event and trigger reminder notifications to attendees.
If a booking is changed, update the calendar event and notify participants automatically.
Consolidate multiple calendars into a single Active Knocker view for team coordination.
In GHL, generate an API key with calendars.write scope and store securely in Active Knocker.
Define the endpoints you will use (for example POST /calendars/) and map fields between Active Knocker and GHL.
Run end-to-end tests for create, read, update, delete flows and monitor for errors before going live.
The Calendars API exposes a set of endpoints that let you create, read, update, and delete calendars, as well as manage groups and resources. It enables you to access calendar data from GHL in a structured, programmatic way. In the Active Knocker context, this means you can automate scheduling and availability workflows without writing code. You can trigger actions from Active Knocker based on lead events and translate those into calendar updates via the API endpoints.
No traditional coding is required thanks to the no‑code capabilities of the integration. You will typically use API keys and OAuth tokens for secure access, then wire up triggers and actions in Active Knocker to call the Calendars API endpoints. Advanced users can extend workflows with custom fields if needed.
Essential scheduling endpoints include POST /calendars/ to create calendars, GET /calendars/ to list calendars, GET /calendars/:calendarId/free-slots to fetch availability, and POST /calendars/groups to organize calendars by group. You may also use PUT and DELETE on specific calendars to update or remove entries.
Authentication is handled via API keys or OAuth tokens. Protect credentials, rotate keys regularly, and apply the principle of least privilege by granting only calendars.write scope where appropriate. Secure storage and encrypted transmission are recommended practices.
Yes. The free-slots endpoint returns available times, enabling real-time scheduling. If a slot is taken, subsequent calls will reflect updated availability, reducing conflicts. Consider caching strategies for performance without sacrificing accuracy.
Field mapping involves aligning Active Knocker fields (like lead name, date, time, attendees) with the corresponding GHL calendar fields. Use consistent data formats (ISO timestamps, email addresses) and validate inputs to ensure clean, reliable automation.
Rate limits depend on the GHL plan and endpoint. Plan for retries with exponential backoff, implement idempotent actions where possible, and monitor usage to avoid hitting limits. If you anticipate high volume, contact support to discuss higher quotas.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
