CRM

GoHighLevel Opportunity Not Created? Why Deals Don’t Appear in Your Pipeline

Workflow should add a deal but nothing shows in the pipeline? Check duplicate settings, Create vs Update actions, pipeline and stage, filters and duplicate contacts.

By Your HighLevel Expert Updated 3 min read

Summary

When a workflow should create an opportunity but nothing appears, the most common cause is that the contact already has an opportunity and duplicates are not allowed, so no new one is made. Other causes: the step is an Update Opportunity action (which never creates), the opportunity went to a different pipeline or stage, the board filters hide it, the workflow did not run, or it is attached to a duplicate contact.

Pipelines are only useful if every lead lands in them. When a workflow is supposed to create an opportunity and nothing appears, it usually is not a bug. HighLevel is protecting you from duplicates, or the deal is somewhere you are not looking.

Short answer Check whether the contact already has an opportunity while duplicates are off. That is the most common cause. Then confirm the step is Create (not Update), the pipeline and stage match the board you are viewing, the board is not filtered, and the workflow actually ran. For a guided version, use the GHL Troubleshooter for opportunities.

1. Does the contact already have an opportunity?

Create Opportunity actions can be set to allow or block duplicates. When duplicates are blocked and the contact already has an opportunity, no new one is created. This is the right default for most businesses (one person, one deal), but it surprises people when a returning lead does not appear as a new card.

What to do:

  1. Open the contact and look at their opportunities, including closed ones.
  2. Decide whether a second opportunity is genuinely wanted. Often it is better to update the existing one, for example move it back to a “New lead” stage.
  3. If a second deal is right, allow duplicates on the action or in the location’s settings.

2. Is the step Create or Update?

An Update Opportunity action only changes an opportunity that already exists. It never creates one. Workflows built by copying another workflow sometimes end up with an update step where a create step was needed. If the contact might not have an opportunity yet, put a Create step first.

3. Was it created in another pipeline or stage?

The opportunity may exist, just not on the board you are looking at. Open the contact’s opportunities list to see where it went, then correct the pipeline and stage on the action. Pipelines with similar stage names (“New Lead” in three pipelines) make this easy to mix up.

4. Is the board filtered?

Board filters for status (open, won, lost, abandoned), owner or date can hide new opportunities. Clear the filters and search for the contact by name.

5. Did the workflow run at all?

If the contact never entered the workflow, no step ran. Check the workflow’s enrollment history and execution log for the contact. If they are not there, the problem is the trigger. The guide on workflows not firing walks through it.

6. Is it attached to a duplicate contact?

If the same person exists twice (for example with two email addresses), the opportunity may sit on the other record. Search by phone and email, merge the duplicates, and fix the form, import or integration that created the second record.

The opposite problem: too many opportunities

If contacts end up with several cards in the pipeline instead, the usual causes are reversed: duplicates allowed, more than one workflow creating an opportunity for the same event, people submitting forms or booking more than once, or duplicate contacts. The fix is to let one workflow create the opportunity and have the others update it.

A simple structure that avoids most problems

  1. One workflow per entry point (form, call, Facebook lead) creates the opportunity in a single “New lead” stage.
  2. Every later workflow (booking, no-show, payment) updates that opportunity’s stage or status.
  3. Duplicate opportunities stay off unless your business really sells repeat deals to the same person.
  4. Duplicate contact settings match how your leads arrive (email-first or phone-first).

When to get help

If several workflows create and move opportunities, the interactions get hard to follow. A structured review of who creates, who updates and which triggers fire usually fixes missing and duplicate deals together. The GHL Troubleshooter can send your answers into a troubleshooting audit request.

Free PDF

Get the GoHighLevel Account Audit Checklist

30 checks to find where your HighLevel account leaks leads, with a “what to fix first” list. Printable, 6 pages.

  • Pipelines, workflows, follow-up and calendars
  • Forms, integrations, SMS/A2P and reporting

One email with the download link. No newsletter, no spam. Privacy

Frequently asked questions

Why didn’t my GoHighLevel workflow create an opportunity?

Most often the contact already has an opportunity and the action does not allow duplicates, so no new one is created. Also check that the step is Create Opportunity (not Update), that the pipeline and stage are the ones you are viewing, and that the workflow actually ran for the contact.

Does Update Opportunity create a new opportunity if none exists?

No. An update action changes an existing opportunity. To make sure one exists, use a Create Opportunity step first.

How do I stop duplicate opportunities in GoHighLevel?

Keep duplicates turned off unless a contact can genuinely have several deals, let one workflow create the opportunity while others update it, and merge duplicate contacts so each person has one record.

Keep reading