How GoHighLevel If Else Conditions Branch Workflows

A contact moving through a GoHighLevel workflow doesn't follow one fixed script. GoHighLevel if else conditions decide, the instant someone reaches that step, whether a contact matches a condition or not.

That decision controls which path they take next: one branch for a match, another for everyone else, instead of running every contact through the same sequence.

A contact can match on a tag, a custom field, a pipeline stage or an appointment status. Anyone who matches nothing falls into the "None" branch GoHighLevel adds by default.

Setting Up GoHighLevel If Else Conditions

Building a branch starts with picking a field, choosing an operator and setting a comparison value. "Add Branch" creates more paths, and a second condition stacks onto the same branch through "Add Segment."

Where a branch carries more than one condition, you choose between AND and OR. AND means every condition in that segment has to hold before a contact qualifies. OR means any single one is enough.

Mix those up and a branch ends up running for almost nobody, or for everybody, which is usually the first sign a workflow needs a second look. The field picker searches across folders and subfolders, and it reaches company-level fields too when a contact is tied to a company record.

Checking a pipeline stage works the same way as checking a tag. The condition doesn't care which kind of data it's reading.

Dynamic Values and the Fields That Just Started Working

As of a September 1, 2026 update to GoHighLevel's documentation, If/Else conditions can compare against dynamic custom values instead of only fixed numbers typed in once. A condition can read a live value carried over from an earlier workflow step, or a stored field that updates on its own.

Numeric, date, select or dropdown, and monetary fields all support this. One catch: a select or dropdown field needs its option ID, not the label a user sees on screen, so a branch built against the visible name quietly never matches.

The same update added Contact Engagement Score, Attribution Medium ID, Note Creator Name and Task ID as fields a branch can check for the first time.

A lead qualification workflow, the kind we built for a law firm's intake process, can now split contacts by how engaged they've actually been instead of a tag someone remembered to apply.

Managing Branches Without Rebuilding Them

GoHighLevel's changelog lists ways to manage existing branches rather than rebuild them from scratch.

• Duplicate a branch, conditions included, through a three-dot menu, so a near-identical path doesn't need reassembling by hand.
• Drag branches into a new order with a dedicated reorder icon.
• Rename the "None" branch, once permanently stuck with that label, to whatever actually describes it.

The AI Builder picked up a related upgrade. It can edit If/Else and Wait actions through conversation, adding or removing branches and updating conditions without dropping into the manual editor.

Before this, building an If/Else action through AI Builder worked fine, but changing it afterward meant leaving the conversation entirely.

Branches still need to connect without duplicating steps, which is what the Go To action is for. It sends a contact to another action already in the workflow, and it can only sit as the final step of a branch, never in the middle of one.

GoHighLevel's own example checks for a Purchased tag. Contacts without it get a reminder sequence, then a Go To step sends them to a wait step that already exists in the other branch.

Getting that branching right across a full client journey is less about any single condition and more about whether the sequence holds together end to end, which is worth having someone familiar with GoHighLevel workflow automation check before it goes live.

Cover photo by Josue Velasquez on Pexels