Authenticate securely using OAuth 2.0 and an API key with scope: opportunities.readonly, enabling read access to opportunities data.
Establish a trusted connection from Acuity Scheduling to GHL by supplying your Acuity API key, and validating via a shared signature or webhook verification.
GET /opportunities/search; GET /opportunities/:id; GET /opportunities/pipelines; POST /opportunities; PUT /opportunities/:id; PUT /opportunities/:id/status; DELETE /opportunities/:id
Trigger: a new Acuity Scheduling appointment creates an opportunity in Opportunities API.
Actions: POST to /opportunities, map customer data, set stage, and assign to owner.
POST /opportunities
name, contact_id, value, pipeline, stage, close_date
Trigger: update in Opportunities API updates a related Acuity Scheduling booking.
Actions: PUT /opportunities/:id/status; update Acuity appointment status.
PUT /opportunities/:id/status
opportunity_id, status, updated_at
Trigger: new opportunity creates follow-up tasks in Acuity Scheduling.
POST /tasks
task_id, oppty_id, due_date, assigned_to
Eliminate manual data entry with real-time sync.
Automate lead-to-booking workflows to close deals faster.
Easily extend with additional endpoints and automation.
Definitions of elements and processes used in the integration, including APIs, endpoints, webhooks, and data mapping.
Application Programming Interface that enables software to communicate and share data.
A specific URL in an API that performs a function and returns data.
A call-back URL that receives events in real time from another app.
Standard for secure delegated access that enables apps to act on a user’s behalf without sharing credentials.
Route new Acuity bookings to the correct pipeline stage using customer data.
Create dashboards that show conversion metrics across scheduling and opportunities.
Notify teams when opportunities move stages or when appointments are booked.
Collect API keys, client IDs, and set necessary scopes for opportunities access.
Choose the endpoints you need and map fields between systems (name, email, date, value).
Test in a sandbox environment, then enable live sync and monitor via logs.
You can set up this integration with no code using the visual builders in the templates. If you want advanced custom mappings, you can extend with small scripts. The no-code approach lets you start quickly and scale as needed.
Basic syncing requires endpoints like GET /opportunities/search, GET /opportunities/:id, and POST /opportunities. These handle retrieval, creation, and updates. You can start with read-only access and expand.
Data is transmitted over TLS with OAuth tokens or API keys. We recommend using scoped access and rotating credentials regularly.
Yes. Field mappings between systems can be customized in the integration settings, including name, email, amount, stage, and close date.
Webhooks notify your app about events in real time. You can configure endpoints to receive appointment bookings, updates, and cancellations.
If an appointment is canceled, the corresponding opportunity can be updated or marked as on hold to reflect the change.
A sandbox or trial environment is available for testing without affecting live data.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
