Scope: opportunities.readonly. Use a secure API key or OAuth token to authorize requests to the Opportunities API.
In Zapier, create or connect your GHL account, then test the connection to verify access to Opportunities endpoints.
GET /opportunities/search — search opportunities; GET /opportunities/:id — retrieve by ID; GET /opportunities/pipelines — view pipelines; POST /opportunities — create; PUT /opportunities/:id — update; PUT /opportunities/:id/status — update status; DELETE /opportunities/:id — delete.
Trigger: A new Opportunity is created in GHL, automatically start a Zapier workflow.
Actions: Create or update Opportunity data in GHL via Zapier.
GET /opportunities/search
id, name, pipeline, stage, close_date, amount
Trigger: Retrieve a specific Opportunity by ID.
Actions: Get, update, or delete a single Opportunity.
GET /opportunities/:id
id, status, value, close_date, owner
Trigger: Load pipelines and their stages to drive workflow automation.
Actions: List pipelines, fetch their stages, and map to Zapier workflows.
GET /opportunities/pipelines
id, name, stages, sort_order
Fast automation: Build workflows without coding.
Centralized data: Syncs across apps in real time.
Scalable processes: Reuse templates for multiple teams.
This glossary explains common terms used when integrating GHL’s Opportunities API with the Zapier App Connector.
Application Programming Interface: a set of rules that allows different software to communicate.
Webhook: a real-time notification sent when an event occurs.
Endpoint: a specific URL for an API function.
OAuth: a standard for authorization that enables secure access.
Create a Zap that converts new leads into opportunities and updates progress automatically as activities happen.
Combine opportunities data with dashboards to monitor pipeline health and forecast revenue.
Use webhooks to notify teams when opportunities move stages, with built-in retry logic.
Obtain your API access and connect the GHL account to Zapier; run a test to verify authentication.
Select endpoints like search, by ID, and pipelines, then map fields to your Zapier actions.
Create sample Zaps, test end-to-end flows, and monitor results.
No formal coding is required to connect. Use Zapier’s built-in app connection and the GHL Opportunities API endpoints to set up triggers and actions. Start with a simple trigger like new opportunities and map the fields to your desired actions. As you gain confidence, expand your Zaps to include updates and status changes.
Authentication uses a secure API key or OAuth token with the scope opportunities.readonly. Always store credentials securely and rotate tokens regularly. In Zapier, test the connection after entering credentials to confirm access to the endpoints.
Begin with GET /opportunities/search to discover records, then use GET /opportunities/:id to fetch specific items, and finally explore GET /opportunities/pipelines to understand the workflow stages. Map fields carefully to your Zapier actions for clean data flow.
Handle errors with built-in Zapier error handling and retry logic. Use exponential backoff settings and meaningful error messages to guide remediation. Log failures for quick debugging.
The API is subject to standard rate limits. If you hit limits, space out requests or queue actions in Zapier to avoid throttling. Consider batching read requests where possible.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
