HighLevel Adds Router Workflow Action for Multi-Branch Execution

TL;DR

HighLevel added a Router workflow action that evaluates all branches and runs matching paths sequentially. Review your existing workflows to see if multi-branch routing can replace redundant branching logic.

Who this affects

HighLevel has not confirmed which specific subscription tiers or sub-account types have access to this feature, nor who can safely ignore it.

What changed

• Added the Router action to workflows, which evaluates all branches and runs each matching branch sequentially from left to right.
• Introduced three branch types: Custom rules, Always run, and Fallback.
• Added drag-and-drop reordering of branches within the Branches list to control execution order.
• Enabled rule configuration under "Only continue if" using fields, operators, and rule groups.
• Added test output detailing Passed status, execution reason, and actual contact values when testing a workflow on a real event.
• Rollout status, plan gating, and replaced or broken legacy features remain unconfirmed by HighLevel.

Where to find it

The feature is located inside Automation > Workflows. When editing or building a workflow, the Router action can be added directly into the action sequence.

How agencies will use this

An agency building a workflow for inbound lead management can use the Router action to run multiple actions on a single contact without building separate parallel workflows.

Inside the sub-account workflow builder, an operator adds a Router action with multiple branches. One branch uses Custom rules under "Only continue if" with specific fields and operators to assign a task when a condition is met. A second branch is set to Always run to log an internal update, while a third branch acts as a Fallback if conditions fail. Using drag-and-drop reordering, the agency sets the left-to-right execution order and validates the logic using Test workflow to inspect the actual contact values and pass reasons on a real event.

Our take

This is marked as a major workflow update. Traditional workflow branches usually route contacts down a single path, forcing agencies to build workarounds when a contact needs to qualify for multiple independent actions. Because HighLevel has not confirmed whether this breaks or alters any existing If/Else logic, treat existing live workflows with caution until you verify the Router behavior in a test workflow.