Authorize access using OAuth2 with the scope opportunities.readonly to securely retrieve data from the Opportunities API.
In the Zapier app, configure OAuth2 (or API key) to grant the connector access to the Opportunities API. Ensure the scope opportunities.readonly is selected during setup.
– GET /opportunities/search — search for opportunities – GET /opportunities/:id — retrieve a single opportunity by ID – GET /opportunities/pipelines — list opportunity pipelines – PUT /opportunities/:id/status — update an opportunity’s status – POST /opportunities — create a new opportunity – PUT /opportunities/:id — update an existing opportunity
Trigger: When new or updated opportunities are detected via the GET /opportunities/search endpoint.
Actions: Retrieve matches, map fields to your app, and optionally create or update local records.
GET /opportunities/search
id, name, pipeline, stage, amount, close_date
Trigger: Retrieve a specific opportunity by ID using GET /opportunities/:id.
Actions: Fetch details, update status via PUT /opportunities/:id/status, or delete via DELETE /opportunities/:id.
GET /opportunities/:id
id, name, pipeline, stage, amount, close_date
Trigger: Retrieve pipelines via GET /opportunities/pipelines.
Actions: Retrieve pipelines and map stages to your Zapier workflows.
GET /opportunities/pipelines
id, name, stages, default_stage
Automate CRM workflows without writing code, saving time and reducing manual data entry.
Keep data synchronized between Opportunities API in GHL and your other business tools.
Trigger real-time alerts and automated updates when opportunities change stage or status.
Overview of the elements and processes used by this integration, including endpoints, triggers, actions, and field mappings.
Definition: The GHL API enables programmatic access to your GHL data via authenticated REST endpoints.
Definition: A specific API path combined with an HTTP method to perform a task.
Definition: OAuth2 protocol used to authorize access securely to the GHL API from the Zapier App Connector.
Definition: Example path illustrating how an endpoint is addressed, such as /opportunities/:id.
Description: When a new lead is captured, automatically create an opportunity in GHL via the Opportunities API and map fields to keep your pipeline fresh.
Description: When a workflow updates a deal stage, push the status to GHL using PUT /opportunities/:id/status.
Description: Create a two-way sync so changes in GHL and your apps reflect across systems in real time.
In the Zapier app, configure OAuth2 and grant the opportunities.readonly scope.
Select GET /opportunities/search, GET /opportunities/:id, and GET /opportunities/pipelines as needed and map response fields.
Create Zaps that trigger on new opportunities, updates to status, or pipeline changes, and use actions to create or update records.
The Opportunities API scope is opportunities.readonly, which allows read access to opportunities data. If you need to create or modify records, you will require write permissions and the appropriate scope. In Zapier, you configure the connection once, authorize the app, and you can select read actions such as search and get-by-id to build your automations.
Available endpoints include search (GET /opportunities/search), retrieve by ID (GET /opportunities/:id), and list pipelines (GET /opportunities/pipelines); you can also create (POST /opportunities), update (PUT /opportunities/:id), update status (PUT /opportunities/:id/status), or delete (DELETE /opportunities/:id). Not all endpoints are required for every page—choose the ones that fit your workflow and map fields accordingly.
Supported authentication methods typically include OAuth2 and API keys; OAuth2 is common in Zapier. Configure your client credentials, set the correct redirect URI, and ensure the scope includes opportunities.readonly (and write) if needed. This keeps your connection secure while enabling your automations.
Yes. If you have write permissions (POST, PUT, DELETE), you can create, update, and delete opportunities via the API endpoints. If your connection is read-only, you can still automate many workflows using read-only endpoints, but you won’t be able to modify data.
Rate limits depend on your GHL plan and API tier. Monitor responses and implement retries in Zapier with exponential backoff. Avoid spamming requests by paginating and staggering calls, and cache results where appropriate.
No extensive coding is required. This is a no-code/low-code integration using Zapier to connect the GHL Opportunities API. You may need to configure field mappings and transforms within Zapier steps, but most workflows can be built through triggers and actions.
In Zapier, use the Test Trigger feature to verify the connection with sample data. You can also run a test action to confirm that GET /opportunities/search, GET /opportunities/:id, or GET /opportunities/pipelines return the expected data and mappings before enabling the automation.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
