Authenticate requests using your GHL access token with the objects/schema.readonly scope. Your app should securely store credentials and rotate them regularly.
Authenticate Acuity requests with your Acuity API key or OAuth credentials, granting access to bookings and client data needed for mapping to GHL Custom Objects.
Endpoints used include: GET /objects/:key, GET /objects, objects/schema.write, objects/record.readonly, GET /objects/:schemaKey/records/:id, objects/record.write, POST /objects/:schemaKey/records, PUT /objects/:schemaKey/records/:id, DELETE /objects/:schemaKey/records/:id. Note: API Endpoint10 through Endpoint17 are not required for this page.
Trigger: New or Updated Booking in Acuity Scheduling
Actions: Upsert a Custom Object in GHL with fields mapped from the booking (client name, email, date, time, service).
POST /objects/{schemaKey}/records
client_email, booking_id, scheduled_time
Trigger: Booking Created or Updated in Acuity
Actions: Create a Client-like object in GHL or enrich an existing contact with Acuity data
POST /objects/{schemaKey}/records
client_email, client_id
Trigger: Acuity booking status changes (confirmed, cancelled)
Actions: Update the corresponding Custom Object record in GHL to reflect current status
PUT /objects/{schemaKey}/records/{id}
appointment_id, status
Real-time data sync between Acuity Scheduling and GHL Custom Objects reduces manual data entry and errors.
Centralized data in a single source enables better reporting, segmentation, and automation.
Faster onboarding for teams and consistent customer journeys across platforms.
This glossary defines core terms used in this guide, including API endpoints, authentication concepts, and data objects.
A RESTful interface in GHL that enables reading, creating, and updating custom object records used to model your business data.
A cloud-based appointment scheduling service that exposes its own API for bookings, clients, and services, which you can connect to GHL via the Custom Objects API.
A specific URL path and HTTP method used to perform an action on an API, such as GET, POST, PUT, or DELETE.
A combined update/insert operation that creates a new record or updates an existing one based on a unique key.
Automatically create a Custom Object in GHL when a new Acuity booking is made, capturing client, time, and service details for follow-up.
Enrich GHL contact records with Acuity data such as upcoming appointments to tailor campaigns.
Trigger automations when bookings change status to drive reminders, reschedules, or cancellations.
Collect your GHL access token with the objects scope and your Acuity API key, then map booking fields to your Custom Object schema.
Create a Custom Object schema in GHL and configure endpoints like POST /objects/{schemaKey}/records and PUT /objects/{schemaKey}/records/{id}.
Run end-to-end tests, verify field mappings, and set up dashboards to monitor sync health and retries.
The Custom Objects API lets you manage structured data used by your business processes within GHL. You can read, create, update, and delete object records and define custom schemas that model your data. This enables you to store appointment-related data as objects that are easy to automate and report on.
Yes, many integrations can be built using no-code features in GHL, including the Custom Objects API. You can set up webhooks or scheduled syncs to move data between Acuity and GHL without writing code. For more complex mappings, a developer can help with advanced field mappings and error handling.
You can sync core fields like client name, email, phone, booking time, service, and status. You can extend with custom object fields as needed. Always align data types and formats (dates, emails) and consider privacy requirements.
A basic integration can be built by a power user, but a developer helps with complex mappings and robust error handling. Use the API reference and examples to accelerate setup.
Webhooks are supported to notify your system of changes, and you can also rely on scheduled syncs for less frequent updates. Depending on your use case, combine both approaches for reliability.
Error handling includes retries with exponential backoff and detailed logging. Use idempotent requests when possible and capture error messages to diagnose issues quickly.
API endpoints and docs live in your GHL developer portal. Look for the Custom Objects API section and the Acuity Scheduling integration page. If something is missing, contact support or consult the API reference for example payloads.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
