GoHighLevel’s Multiple Opportunities setting controls whether a workflow can create more than one opportunity for the same contact in the same pipeline and stage. The setting is useful when one person or company can generate several legitimate deals, projects, orders, or service engagements over time.
It should not be enabled simply because duplicate opportunities are technically possible. The correct choice depends on what an opportunity represents in your operating process. If each opportunity is a distinct piece of business, allowing multiple records can preserve useful history. If an opportunity represents the contact’s single active sales relationship, creating another record can damage ownership, reporting, and follow-up.
The practical rule is straightforward: turn Multiple Opportunities on when repeated opportunities represent separate business states, and leave it off when the workflow should maintain one opportunity for the matching contact, pipeline, and stage. Then test the workflow with realistic repeat and non-repeat scenarios before relying on its reports.
What Multiple Opportunities means in GoHighLevel
A contact is the person or company record in GoHighLevel. An opportunity is a specific sales, service, or commercial record associated with that contact. A pipeline organizes opportunities, while a stage describes where an opportunity is in that pipeline.
Those objects are related, but they are not interchangeable. One contact may legitimately have several opportunities. For example, a business owner could request separate proposals for two locations, place another order after an earlier purchase, or begin a new project while an existing project is still open.
By contrast, some processes treat the opportunity as the contact’s one active deal. In that model, creating a second record for the same contact in the same pipeline and stage usually creates ambiguity. The team may not know which record owns the next action, and management may count one commercial relationship twice.
Multiple Opportunities is a record-creation decision, not merely a convenience setting. Decide what each opportunity means before deciding whether the workflow should create another one.
What the toggle changes in a workflow
The Multiple Opportunities option is configured within an opportunity-related workflow action, such as Create/Update Opportunity. This means the behavior is determined by the specific automation step, not necessarily by a single global rule for every workflow in the account.
When the option is enabled, the action can create a new opportunity for a contact even when a matching opportunity already exists in the selected pipeline and stage. This supports repeat transactions and parallel engagements, provided the workflow runs with a legitimate reason to create another record.
When the option is disabled, the action follows the single-opportunity behavior for the relevant contact, pipeline, and stage. Instead of creating another matching opportunity, the workflow generally works with the existing record and applies the configured updates. The exact outcome should be confirmed in a test sub-account or with a controlled test contact, especially when several workflows affect the same pipeline.
The toggle does not replace workflow logic. It does not decide whether a contact is a new customer, whether an order is genuinely separate, or whether an old opportunity is closed. Those decisions must be represented by triggers, conditions, fields, stages, and ownership rules around the opportunity action.
When to enable Multiple Opportunities
Enable the setting when each workflow run can represent a distinct business event. Common examples include recurring services, repeat purchases, separate projects, multiple properties, or a new inquiry after a previous deal has ended.
- Repeat sales: A customer can buy the same or another service more than once.
- Parallel projects: The same company can have several independent engagements.
- Location-based work: Each site, branch, or property requires its own commercial record.
- Recurring requests: Each booking, renewal, or service request needs separate ownership and reporting.
In these cases, merging every event into one opportunity can be just as harmful as creating duplicates. A single record may lose the history, value, timing, and responsibility associated with each distinct engagement.
When to leave it disabled
Leave Multiple Opportunities off when the business process expects one active opportunity per contact in a pipeline and stage. This is common for a straightforward lead-to-sale process where a contact should move through one sequence from qualification to close.
It is also safer to leave it off when a workflow may run more than once for technical reasons, such as a contact receiving the same tag again, a form being submitted twice, or two automations responding to the same event. In those cases, allowing every execution to create a new record can turn a workflow retry into a reporting problem.
Separate business event
Use it when the new opportunity needs its own value, stage history, owner, next action, and outcome.
Same business event
Keep one opportunity when the workflow is continuing, correcting, or updating an existing deal.
How to enable Multiple Opportunities in GoHighLevel
- Open the relevant GoHighLevel sub-account.
- Go to Automation and open Workflows.
- Select the workflow that creates or updates the opportunity.
- Add or open the relevant Create/Update Opportunity action.
- Review the pipeline, stage, opportunity name, owner, value, and other fields used by the action.
- Locate the Multiple Opportunities setting.
- Turn it on if each qualifying workflow run should create a separate opportunity.
- Leave it off if the action should reuse or update an existing matching opportunity.
- Save the action, save the workflow, and run controlled tests before activating the process broadly.
The important step is not locating the toggle. It is defining the condition that makes a new opportunity legitimate. A workflow that creates a new record every time it runs is only correct if every run represents a new business event.
A simple decision sequence for workflow design
Use this sequence before turning the setting on:
This sequence separates the business decision from the platform setting. It also exposes a common design error: using a contact as a substitute for an opportunity. A contact can remain the same while the commercial relationship changes several times.
Make multiple opportunities understandable to the team
Multiple records are only useful if a person can distinguish them quickly. Use consistent opportunity names and fields that explain why the record exists. Depending on the process, that may include a project label, location, product, order reference, service period, or expected start date.
Ownership should also be explicit. If two opportunities belong to different people, regions, or service teams, the workflow should assign ownership using a clear rule. Otherwise, enabling multiple opportunities may preserve separate records while still creating an unclear handoff.
Separate opportunity records improve reporting only when the team can identify the difference between them. More records without naming, ownership, and stage discipline create more ambiguity, not more visibility.
Stages should represent meaningful business states rather than activities. “Proposal sent” may be a useful state if it changes forecast or ownership. “Email sent” is usually an activity and may not justify moving or creating an opportunity. This distinction helps prevent workflow actions from creating records for events that do not represent a new deal.
Testing and troubleshooting duplicate opportunities
Test the workflow with at least four controlled cases:
- Run the workflow for a contact with no matching opportunity.
- Run it again for the same contact with Multiple Opportunities off.
- Run a legitimate second business event with the setting on.
- Trigger the same event twice to see whether an accidental duplicate is created.
- Review the opportunity owner, name, value, stage, notifications, and reporting after each test.
If unexpected records appear, inspect every workflow that can create or update opportunities for the same contact and pipeline. Check whether a form, tag, webhook, integration, manual action, or repeated trigger is also starting an opportunity action. The setting may be correct while the trigger design is not.
If an expected second opportunity does not appear, confirm that the workflow actually reached the opportunity action, that the action targets the intended pipeline and stage, and that Multiple Opportunities is enabled in that specific action. Also check whether an earlier condition, wait step, or workflow path prevented execution.
A useful diagnostic question is: What business event should this opportunity represent, and where is that event stored? If the team cannot answer that question, the workflow is probably creating records without a reliable business key.
How this fits into a broader CRM design
Multiple Opportunities is one small setting inside a larger CRM model. Before changing it, document the contact, opportunity, pipeline, stage, owner, and reporting relationships. Then decide which events create records and which events only update them.
If your GoHighLevel account has inconsistent pipelines, repeated records, or unclear handoffs, the underlying issue may be CRM architecture rather than one toggle. A process-first CRM consulting approach can help define record boundaries, ownership rules, automation conditions, and reporting requirements before the workflow is rebuilt.
GoHighLevel automation should support a clear operating process. More opportunities, more workflows, or more tools do not automatically create better visibility. The useful configuration is the one that makes the current business state clear to the person responsible for the next decision.
An opportunity should be created because a meaningful business event occurred, not because a workflow happened to run again.
Frequently asked questions
What does Multiple Opportunities do in GoHighLevel?
It allows an opportunity workflow action to create another opportunity for the same contact in the same pipeline and stage when the setting is enabled. When disabled, the workflow generally works with the existing matching opportunity instead of creating another one.
Should I enable Multiple Opportunities for every GoHighLevel workflow?
No. Enable it only when each qualifying workflow run represents a separate deal, project, order, location, or service engagement. Leave it disabled when the workflow should maintain one active opportunity and update it over time.
Can one GoHighLevel contact have multiple opportunities?
Yes. A contact can be associated with multiple opportunities when the business process has separate commercial events. Each opportunity should have enough naming, ownership, stage, and field information to distinguish it from the others.
Why is GoHighLevel creating duplicate opportunities?
Possible causes include Multiple Opportunities being enabled, repeated workflow triggers, duplicate form or webhook events, manual creation, or another automation acting on the same contact and pipeline. Review all opportunity actions and test the trigger path.
How should I test Multiple Opportunities in GoHighLevel?
Use a controlled test contact and check first-run, repeat-run, legitimate second-event, and accidental-repeat scenarios. Review the resulting records, owners, stages, notifications, and reports before applying the workflow to live contacts.
Make your GoHighLevel pipeline reflect the real process
If opportunity records, workflow triggers, or ownership rules are difficult to interpret, ConsultEvo can help clarify the CRM structure and automate it around meaningful business events.
