Authenticate using your GHL API key with the scope locations/customValues.readonly. Use OAuth where supported, and ensure your account has access to the customValues and customFields endpoints for Acuity Scheduling integration.
Acuity Scheduling relies on the connector’s credentials to access and sync data. Ensure the Acuity Scheduling app is authorized and that callbacks from GHL are allowed for secure data transfer.
– GET /locations/:locationId/customValues – GET /locations/:locationId/customValues/:id – locations/customValues.write – POST /locations/:locationId/customValues – PUT /locations/:locationId/customValues/:id – DELETE /locations/:locationId/customValues/:id – locations/customFields.readonly – GET /locations/:locationId/customFields – GET /locations/:locationId/customFields/:id – GET /custom-fields/:id – GET /custom-field/object-key/:key – locations/customFields.write – POST /locations/:locationId/customFields – PUT /locations/:locationId/customFields/:id – DELETE /locations/:locationId/customFields/:id – locations/tags.readonly – GET /locations/:locationId/tags
Trigger: When a location is used in Acuity Scheduling or its data changes, pull the latest custom values from GHL to keep booking forms in sync.
Actions: GET /locations/:locationId/customValues and GET /locations/:locationId/customValues/:id
Methods: GET
Key fields: locationId, id, value
Trigger: Add or modify fields to capture booking-specific data in Acuity Scheduling.
Actions: POST /locations/:locationId/customFields, PUT /locations/:locationId/customFields/:id, DELETE /locations/:locationId/customFields/:id, GET /locations/:locationId/customFields
Methods: POST, PUT, DELETE, GET
Key fields: locationId, id, fieldKey, fieldValue
Trigger: Retrieve global fields and tags to standardize data before syncing to Acuity Scheduling.
Actions: GET /customFields, GET /customFields/:id, GET /locations/:locationId/tags
Methods: GET
Key fields: locationId, fieldId, tagId
Automate data flow between Acuity Scheduling and GHL without writing code.
Keep field data consistent across apps with real-time synchronization and mapping.
Scale campaigns and reports with dynamic fields that reflect your locations’ setups.
This glossary defines terms such as GHL API, Custom Field, Custom Value, Endpoint, and Location as they relate to the integration.
Programmatic access to your GHL data, including endpoints for locations, custom values, and fields.
A specific URL path that enables operations like GET, POST, PUT, and DELETE against your data.
A field definition stored in GHL used to collect specific data about a contact, lead, or location.
A grouping in GHL where related fields and data points are managed for a site or account.
Automatically populate Acuity Scheduling forms with GHL custom values to tailor each booking page to location and service.
Use tags to segment customers in GHL based on Acuity Scheduling field values for smarter follow-ups.
Track field changes over time and feed analytics dashboards to measure service performance and bookings.
Collect your GHL API key and ensure Acuity Scheduling is authorized to access your GHL data within the App Connector.
Enable the necessary endpoints (customValues, customFields, and tags) in your GHL settings and in the App Connector for Acuity Scheduling.
Run test synchronizations, verify data integrity, and review logs to confirm everything is wired correctly.
The Custom Fields API is a programmatic interface that lets you read and write field data across GHL. It exposes endpoints to fetch custom values, custom fields, and tags, which you can use to enrich Acuity Scheduling bookings. With proper scopes, you can pull location-specific values and keep forms aligned with your data model. This API enables automation and reduces manual data entry by syncing essential fields between GHL and Acuity Scheduling.
No extensive coding is required if you use the App Connector and a no-code automation platform. You can configure API calls, map fields, and route data between GHL and Acuity Scheduling using pre-built actions. For advanced workflows, you can add lightweight scripts or a Zapier flow to customize processing. If you prefer fully custom logic, you can implement endpoints directly and handle responses in your integration flow.
Key endpoints include: GET /locations/:locationId/customValues, GET /locations/:locationId/customFields, GET /locations/:locationId/tags, and GET /custom-fields/:id. These allow you to read existing values, read and write fields, and tag bookings. Depending on the use case, you may also rely on POST, PUT, and DELETE variants for managing data. The exact endpoints you use depend on whether you’re syncing values, fields, or tags for Acuity Scheduling.
Authentication uses your GHL API key with the appropriate scopes or OAuth where available. Ensure your App Connector is authorized to access the customValues, customFields, and tags endpoints. In Acuity Scheduling, confirm the connected app is allowed to perform read/write operations as required by your workflow. Always protect credentials and rotate keys per your security policy.
Yes. You can update Acuity Scheduling fields from GHL by using the PUT and POST endpoints for customFields and the related endpoints for customValues. Map the response data to Acuity Scheduling field keys and ensure you handle conflicts or field existence checks. Test updates in a staging environment before rolling out to production.
Rate limits depend on your GHL plan and API usage. If you anticipate high call volume, implement batching, caching, and exponential backoff in your integration. Monitor API usage via the developer dashboard and optimize request payloads to stay within limits. For heavy usage, consider spreading calls over time or using webhooks where supported.
Mapping involves aligning GHL field keys with Acuity Scheduling field identifiers. Create a mapping table that translates GHL customValue and customField keys to Acuity fields, then apply transforms as needed (e.g., date formats, string normalization). Validate mappings with sample bookings to ensure accuracy, and adjust as your data model evolves.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
