To read opportunities, obtain an OAuth token with the opportunities.readonly scope from your GHL developer portal and use it in your Zapier connection.
In Zapier, add a connection to your GHL account using OAuth credentials and select the Opportunities API scope for read access and future writes as needed.
GET /opportunities/search — search for opportunities GET /opportunities/:id — retrieve an opportunity by ID GET /opportunities/pipelines — retrieve all pipelines POST /opportunities — create a new opportunity PUT /opportunities/:id — update an existing opportunity PUT /opportunities/:id/status — update the status of an opportunity DELETE /opportunities/:id — delete an opportunity opportunities.write — write permission to modify opportunities in GHL
Trigger on new or updated opportunities in GHL and pull details via GET /opportunities/search or GET /opportunities/:id.
Push updates to external systems, create tasks, and keep data in sync across apps.
GET /opportunities/search and GET /opportunities/:id as needed.
id, name, stage, value, close_date, pipeline_id
Trigger when you want to export or sync pipelines for reporting in a dashboard.
Use GET /opportunities/pipelines to pull pipelines, map to reports, and update CRM records as needed.
GET /opportunities/pipelines
pipeline_id, stage_id, name, opportunity_count
Trigger external changes to update opportunity status in GHL.
Call PUT /opportunities/:id/status to reflect updates in GHL, then propagate to connected apps.
PUT /opportunities/:id/status
id, status, updated_at
Automate data flow between GHL and your apps without writing code.
Build multi-app workflows with triggers and actions across your stack.
Access ready-made endpoints to accelerate integration projects.
This section outlines core elements and processes used in this integration between GHL and Zapier App Connector.
GHL API is the programmatic interface that lets apps read and update data like opportunities, contacts, and pipelines in your GHL account.
Opportunities represent potential deals in GHL and are tracked through stages in pipelines.
Zapier App Connector enables connecting apps to GHL via OAuth and API calls to automate workflows.
OAuth scopes define allowed actions, such as reading opportunities (opportunities.readonly) or creating/updating data.
Set up triggers to score opportunities and update lead status automatically in downstream apps.
Pull pipeline data into dashboards to monitor win rates and cycle times without manual CSVs.
Create tasks in your CRM or support tool when opportunities move stages to keep teams aligned.
Obtain OAuth tokens for opportunities.readonly and connect the integration in Zapier.
Map GET /opportunities/search and GET /opportunities/:id to your workflows and select fields to sync.
Run test requests, validate data, and deploy your automations to production.
The Opportunities API is a GHL API that lets you read and manage opportunities in your GHL account. Access requires OAuth tokens scoped to opportunities.readonly for read operations. To connect with Zapier App Connector, create a connection in Zapier, authorize, and select the Opportunities API scope. Then you can trigger and act on opportunities in your automations.
No traditional coding is required; Zapier App Connector handles orchestration. You can use simple maps and filters to pass data between GHL and apps; for advanced logic, you can use built-in Formatter and Paths.
Supported endpoints include search, get by id, pipelines, create, update, status, and delete for opportunities. Additional endpoints may exist; refer to developer docs for the full list.
Authenticate via OAuth; use secure connections; rotate tokens; never expose secrets. In Zapier, the connection widget handles token refresh automatically and token storage is managed by Zapier.
Yes. Use PUT /opportunities/:id/status or POST /opportunities to update records. Map status field to your external system and test the updates with sample data.
Common fields to map include id, name, status, pipeline, stage, value and close_date. Also consider fields like owner_id, last_modified or custom fields depending on your workflow.
Rate limits and error messages are documented in the API docs; expect common HTTP codes like 200, 401, 403, 429. For errors, check error.response and implement retry/backoff in your Zapier automations.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
