GoHighLevel and Zapier use pipeline and stage values to decide where an opportunity should be created or updated. The visible names, such as a pipeline called New Business or a stage called Qualified, are designed for people. Zapier may also need the internal identifiers associated with those records.
The safest way to find these values is to configure a GoHighLevel opportunity action in Zapier, select the connected location, and use the Pipeline and Stage fields that Zapier loads from that account. Select the pipeline first, then choose a stage from that pipeline. This lets Zapier use the correct internal values without relying on copied text or guessed IDs.
The important operational point is that an ID is only useful when it is tied to the correct GoHighLevel location and business meaning. A technically valid ID can still route an opportunity incorrectly if the pipeline, stage, or ownership logic is wrong.
What pipeline and stage IDs mean in GoHighLevel
A GoHighLevel pipeline represents a business process, such as new sales, renewals, recruiting, or onboarding. Stages are the meaningful states within that process. For example, a sales pipeline might contain New Lead, Qualified, Proposal Sent, and Won.
GoHighLevel assigns internal identifiers to pipelines and stages. Zapier uses those identifiers when an action creates or updates an opportunity. The Zapier editor often presents a readable label, but the value passed behind the scenes can be an internal ID rather than the label itself.
A pipeline stage should represent a meaningful business state, not merely the last activity someone performed.
This distinction matters because names can be changed, repeated across locations, or interpreted differently by different teams. The ID provides a system reference, while the selected pipeline and stage provide the business meaning. Both need to be correct.
Before looking for an ID
Prepare the workflow before opening the Zapier field. This avoids solving a mapping problem when the underlying process is still unclear.
- Confirm that the correct GoHighLevel location is connected to Zapier.
- Confirm that the target pipeline already exists in that location.
- Confirm that the required stages belong to that pipeline.
- Decide what event should create or update the opportunity.
- Define who owns the opportunity after it is routed.
Pipeline and stage choices are location-specific. A pipeline with the same name in another GoHighLevel location may have a different internal ID. Treat the location connection as part of the mapping, not as a minor account setting.
How to find a GoHighLevel pipeline ID in Zapier
Depending on the current Zapier and GoHighLevel interface, the option may show a name, an ID, or a combined value. Do not assume that the visible label is the complete value being sent. The reliable action is to select the pipeline from the loaded list rather than manually typing a name.
If you need the raw ID for documentation or another technical step, inspect the field value available in Zapier after selection. The editor may expose it in a field detail, test output, or mapped value. The interface can change, so the exact display should not be treated as permanent.
How to find a GoHighLevel stage ID in Zapier
Stage selection should follow pipeline selection. Zapier needs to know which pipeline is selected before it can return the relevant stages.
- Remain on the same GoHighLevel opportunity action setup screen.
- Open the Stage or Stage ID field after choosing the pipeline.
- Wait for Zapier to load the stages associated with that pipeline.
- Choose the stage that matches the intended business state.
- Check the selected value and test the action before publishing the Zap.
For example, if a lead has completed qualification, the correct stage may be Qualified. If the source system only indicates that a form was submitted, moving the opportunity directly to Qualified may overstate the sales process. The stage should reflect the evidence available in the trigger data.
Choosing a stage by name is not enough. The trigger should contain enough evidence to justify the business state that the stage represents.
Pipeline ID versus stage ID
The process container
The pipeline ID identifies the broader workflow where the opportunity belongs. It answers, “Which process is this opportunity part of?”
The current business state
The stage ID identifies the opportunity’s position within that pipeline. It answers, “What state is this opportunity in now?”
These values are related but not interchangeable. A stage from one pipeline should not be treated as a valid stage for another pipeline simply because the names look similar. When an automation maps both fields, the pipeline should be selected first and the stage should be loaded from that selection.
How to test the mapping before turning on the Zap
A successful Zapier test only proves that the action executed. It does not always prove that the opportunity landed in the right business state. Test the result in GoHighLevel as well.
- Use a controlled test contact or opportunity.
- Run the Zap with a known trigger value.
- Open the resulting opportunity in the connected GoHighLevel location.
- Confirm the pipeline and stage.
- Check the opportunity owner, contact association, title, and other mapped fields.
- Confirm that later workflow actions did not move the opportunity unexpectedly.
If the opportunity appears in the wrong pipeline, first check the connected location and the selected Pipeline field. If it appears in the right pipeline but the wrong stage, inspect the Stage field and any later automation that may update the record.
Common problems with GoHighLevel IDs in Zapier
The dropdown is empty
An empty list can indicate that the GoHighLevel account is not connected to the intended location, that the action does not have the required access, or that the field has not refreshed after a configuration change. Reopen or refresh the field, then verify the selected account and location.
The stage list does not match the pipeline
Re-select the pipeline before loading the stage field. A stale Zapier field can retain an earlier selection, especially after pipelines or stages are changed in GoHighLevel. Also check that the stage was created inside the selected pipeline rather than another one with a similar name.
The Zap runs but the opportunity is routed incorrectly
Compare the Zapier action inputs with the resulting GoHighLevel record. Check for a later Zap step, a GoHighLevel workflow, or a default value that changes the pipeline or stage after creation. The first action may be correct while a later rule changes the final state.
A copied ID no longer works
Do not assume that an ID copied from another location, account, or old Zap is reusable. Reopen the current action and select the value from the available list. Keep documentation tied to the GoHighLevel location and review it after structural changes.
When an opportunity lands in the wrong stage, inspect the decision path before replacing the ID. The mapping may be valid while the business rule is not.
A practical operating rule for opportunity routing
Use this sequence when designing or reviewing a Zap:
- Identify the source event. What happened in the source system?
- Define the destination process. Which GoHighLevel pipeline should own the opportunity?
- Define the justified state. Which stage is supported by the available evidence?
- Assign ownership. Who is responsible for the next action?
- Test the resulting record. Does the opportunity show the expected state and owner?
This sequence separates data mapping from process design. Zapier can move data reliably, but it cannot decide whether a lead is truly qualified unless that decision has been defined in advance.
Consider a hypothetical example. A website form submits a request for a product demonstration. The Zap could create an opportunity in a New Business pipeline and assign it to New Lead. A separate qualification action could later move it to Qualified. Sending it straight to Qualified because the form was completed would make reporting look stronger than the underlying process.
- Correct GoHighLevel location is connected.
- Pipeline was selected from Zapier’s loaded options.
- Stage was selected after the pipeline.
- Stage reflects a real business state.
- Opportunity owner is explicit.
- Test record was checked inside GoHighLevel.
- Later workflows cannot silently undo the intended mapping.
Keeping IDs and CRM automation maintainable
Use readable names for people and internal IDs for system references. Document the location, pipeline name, stage name, purpose, owner, and the Zap that uses the mapping. This makes changes easier to review without forcing every operator to interpret an isolated identifier.
Review dependent Zaps when a pipeline or stage is renamed, removed, reordered, or replaced. A name change may not break an ID-based mapping, but it can still confuse users and reports. A deleted or recreated object can require a fresh selection because the replacement may have a different ID.
For broader workflow design, Zapier automation consulting can help clarify the trigger, decision logic, data mapping, and exception handling. If the larger problem is inconsistent pipeline structure or unclear ownership, CRM consulting is the more appropriate starting point.
The goal is not to collect IDs. The goal is to make opportunity movement predictable, explainable, and owned. More automation steps do not compensate for an unclear sales process.
Frequently asked questions
Where do I find a GoHighLevel pipeline ID in Zapier?
Open a GoHighLevel opportunity action in Zapier, choose the correct connected location, and open the Pipeline field. Select the intended pipeline from the options Zapier loads. The raw ID may be visible in the selected value or test details, but selecting the option is usually sufficient for the action.
Where do I find a GoHighLevel stage ID in Zapier?
Choose the pipeline first, then open the Stage field in the same opportunity action. Zapier should load the stages associated with that pipeline. Select the stage that represents the intended business state and test the resulting opportunity in GoHighLevel.
Why is the GoHighLevel stage dropdown empty in Zapier?
Check that the correct GoHighLevel account and location are connected, that the pipeline has been selected, and that the field has refreshed. The stage may also belong to a different pipeline or the connected account may not have the required access.
Can I manually type a GoHighLevel pipeline or stage ID into Zapier?
You may be able to map or enter an ID in some Zapier configurations, but selecting the value from the loaded field is safer. Manually copied IDs can belong to another location or an object that has since been replaced.
Why does my opportunity reach the wrong GoHighLevel stage even when the Zap succeeds?
Review the selected pipeline and stage, then check later Zap steps and GoHighLevel workflows. A successful Zap run confirms execution, not necessarily that the final business state is correct.
Make GoHighLevel opportunity routing dependable
If pipeline IDs, stage mappings, ownership rules, or downstream workflows are difficult to maintain, ConsultEvo can help turn the process into a clear, testable CRM workflow.
