Authenticate requests to the Calendars API using your GHL API key with the calendars.write scope enabled. Store credentials securely and rotate keys regularly.
Authorize 123FormBuilder to access Calendars API by using an OAuth token or API key. Keep credentials secure and refresh tokens as needed.
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, 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 form submission creates or updates a calendar event in Calendars, then sync the change back to the form data.
Actions include: create calendar, update calendar details, fetch available time slots, and map responses back to 123FormBuilder.
Use POST /calendars/ to create and PUT /calendars/:calendarId to update existing records, enabling real-time sync with form submissions.
Key fields: calendarId, title, startTime, endTime, location, attendees
When a new group is created in 123FormBuilder, automatically mirror the group in Calendars and assign access levels.
Actions: create or update groups, validate slugs, and adjust group status as needed.
Endpoints: POST /calendars/groups, POST /calendars/groups/validate-slug, PUT /calendars/groups/:groupId, PUT /calendars/groups/:groupId/status, DELETE /calendars/groups/:groupId
Group fields: groupId, slug, name, status
Trigger: application requests a resource type; Calendar data is pulled and mapped for use in forms.
Actions: fetch resources, interpret resourceType, and provide ready-to-use data mapping for 123FormBuilder fields.
GET /calendars/resources/:resourceType
Key fields: resourceType, data, availability, permissions
Build and automate calendars without writing code.
Seamlessly automate scheduling workflows between forms and calendars.
Keep data in sync across apps with minimal setup and maintenance.
Definitions of elements, endpoints, and processes used throughout the Calendars API and 123FormBuilder integration.
A calendar is a collection of events and available time slots that can be created, read, updated, or deleted via API endpoints.
A resource is a data type exposed by the API (e.g., calendars, groups, or endpoints) that can be read or written depending on permissions.
An endpoint is a URL path that performs a specific API operation (GET, POST, PUT, DELETE).
A slug is a URL-friendly identifier used to name a calendar group or resource.
Map form submissions to calendar events, creating new slots automatically.
Assign groups and permissions from 123FormBuilder to GHL calendars for accurate access control.
Query free-slots endpoints to present live availability in forms.
Obtain API keys for GHL and App, and install the credentials in your integration settings.
Choose endpoints and set field mappings between calendars and forms.
Run tests, verify data flow, and push to production.
The Calendars API in GHL lets you create, read, update, and delete calendars and events from within 123FormBuilder. By connecting these endpoints, you can drive calendars directly from form submissions, making scheduling seamless and automated. With implementation, you can automate event creation and updates without touching code.
Authentication is required to secure data exchange. Use a GHL API key with the calendars.write scope to create and modify calendars, and use an OAuth token or API key from 123FormBuilder to authorize requests from your forms. Rotate credentials regularly and store them securely.
For basic calendar creation and updates you will mainly use POST /calendars/ and PUT /calendars/:calendarId. Other endpoints like GET /calendars/ help you read and verify data as you build flows. Start with these core endpoints to establish your flow.
Yes. The integration can fetch free-slot data via GET /calendars/:calendarId/free-slots and map it to available options in your forms, enabling real-time scheduling. You can also retrieve group information with GET /calendars/groups to control access or visibility in the user experience.
Field mapping is done in the integration settings by pairing form fields (e.g., event title, date, time, attendees) with the corresponding API fields (title, startTime, endTime, attendees). Testing your mappings with sample submissions helps verify that the data flows correctly and that time zones are handled consistently.
No-code integrations reduce development time, lower maintenance costs, and empower non-technical teams to automate scheduling tasks. They also provide a visual workflow that you can adjust on the fly, making it easier to scale to new calendars, groups, or resources without code.
Start with a small pilot: connect one calendar and a simple form, then test end-to-end data flow and error handling. When you’re ready, gradually expose more endpoints, monitor logs, and implement alerts to catch issues before users are impacted.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
