Router Action

Modified on: Sun, 8 Nov, 2026 at 3:04 PM

The Router action in HighLevel Workflows runs every branch whose conditions match a contact. Learn how to configure multiple paths, control their order, test the results, and publish the workflow.

Table of Contents


What Is the Router Action?

The Router action sends a contact down every branch whose conditions match. The branches run one after another, from left to right. Use it when one contact can qualify for more than one path, such as a form lead who picks several services at once.

Router belongs to the same family as If/Else. The difference is how many branches run. If/Else sends the contact into the first branch that matches and ignores the other branches, even when the contact matches them too. Router checks every branch and runs each one that matches.


Key Benefits of the Router Action

The Router action can handle several matching conditions in one workflow, making complex follow-up processes easier to manage without creating separate workflows for every combination.

  • Every match runs: a contact who matches three branches goes into all three, not only the first one.

  • Predictable order: branches run from left to right, and you can drag them into the order you need.

  • Three branch types: use Custom rules, Always run or Fallback to decide when each branch runs.

  • Familiar conditions: build each rule with fields, operators, conditions and rule groups.

  • Fewer duplicate workflows: one Router replaces extra branches or workflows that you built to catch a second or third match.

  • Clear test results: the test output shows which branch conditions passed and why.

Action Name

The action name identifies the Router on your workflow canvas and helps your team recognize the step when editing or reviewing a workflow.

Router


Action Description

The action description summarizes what happens to a contact when the Router evaluates its branches.

Send the contact down every branch whose conditions match. Branches run one after another, left to right.


Action Details

These settings define the Router and its branches. Review which fields are required before configuring the conditions that determine each path.

FieldDescriptionMandatory
Action NameThe name shown on the workflow canvas. Defaults to “Router”.Yes
BranchesThe list of branches in this Router, in run order. Use Add branch to add a branch, the drag handle to change the order, and the delete icon to remove a branch.Yes
Branch NameThe name of the branch, for example “Branch 1”. It shows on the canvas above the branch.Yes
Branch TypeCustom rules: runs only when the conditions below match. Always run: runs for every contact, with no conditions. Fallback: runs only when no other path matched.Yes
Only continue ifShown for Custom rules. The conditions the contact must match. Select a field, select an operator and enter a value. Use Add condition and Add rule group for more conditions.Yes, for Custom rules

How to Configure the Router Action

The steps below follow the most common journey: a trigger brings in a contact, and the Router sends that contact into each branch it matches.

Step 1: Add the Router Action

Start in the sub-account where you want to create or update the workflow.

  1. From your HighLevel Sub-Account, go to Automation > Workflows.
  2. Open an existing workflow or create a new one.
  3. In the workflow builder, click the + icon where you want to add the Router.
  4. In the Actions panel, search for Router and select it.

The Router appears on the canvas with its branches below it.

Step 2: Open a Branch

In the Router panel, the Branches list shows every branch. Click a branch to open its settings. Enter a Branch Name. Click Back to branches to return to the list.


Step 3: Choose the Branch Type

Open the Branch Type dropdown and select one option:

  • Custom rules: the branch runs only when the conditions below match.

  • Always run: the branch runs for every contact, with no conditions.

  • Fallback: the branch runs only when no other path matched.


Step 4: Set the Conditions

For Custom rules, define what a contact must match under Only continue if. The Router evaluates these conditions to determine whether the branch runs.

  1. Select a contact field or custom field.

  2. Choose an operator: is, is not, contains, does not contain, is any of (comma separated), is none of (comma separated), or is not empty.

  3. Enter the value to compare against the contact field.

  4. Use Add condition or Add rule group if you need additional conditions.

  5. Save the branch.

router-1-branch-rules.gif — Router workflow canvas with conditional branches for different services.

Router showing branches with different service conditions and a fallback path.

Step 5: Add More Branches

Click + Add branch on the canvas, or Add branch in the Branches list. Set the Branch Name, the Branch Type, and the conditions for each new branch. Add as many branches as your use case needs.


Step 6: Set the Run Order

Branches run from left to right. To make a branch run first, drag it by its handle to the top of the Branches list. The canvas updates to show the new order.

router-2-reorder.gif — Router setup panel showing branch order controls.

Use the drag handles in the Branches list to change which matching branch runs first.


Step 7: Save and Add the Next Steps

Click Save action. Then click the + icon under each branch and add the actions that branch should run, such as a note, an internal notification, a tag, or a task.


Router Behavior and Logic

Understanding how matching, branch order, and fallback behavior work helps you predict which actions a contact will enter and in what sequence.

RuleWhat happens
Which branches runEvery branch whose conditions match runs. A contact who matches three branches goes into all three.
Run orderMatching branches run one after another, from left to right. The order in the Branches list is the run order.
Custom rulesThe branch runs only when the contact matches its conditions.
Always runThe branch runs for every contact, with no conditions.
FallbackThe branch runs only when no other path matched.
Compared with If/ElseIf/Else runs only the first branch that matches. Router runs every branch that matches.

Testing the Router

Test the Router with a real workflow event to confirm which branches run and why. Whole-workflow testing lets you inspect the results of the Router step within the full workflow sequence.

  1. In the workflow builder, click Test workflow in the upper-right corner.

  2. On the New test tab, select Test using events.

  3. Under Select Trigger, choose the workflow trigger.

  4. Under Select event, choose a recorded event. If needed, enable Listen for events and trigger a new event.

  5. Review the event data and click Start test run.

  6. When the test finishes, click the Router step on the canvas.

  7. Open Output to review the branch conditions, their results, and why they passed or did not match.

For example, if a contact selects HVAC, Plumbing, and Electrical, the output shows the matching conditions for all three branches.

Important: Workflow tests execute real actions. Use test data to avoid sending unintended messages or modifying customer records.

router-4-test-result.gif — Router action Test tab showing branch condition inputs.

Router action's Test tab showing branch condition inputs. This is an individual-action test view, not the completed whole-workflow test output.

After confirming that the expected branches ran, save and publish your workflow.


Use Case: Route a Lead to Multiple Service Teams

A multi-service request is a practical example of why a Router is useful: one lead may need different teams to complete follow-up actions.

Scenario: a home services business asks one question on its form: “What service do you need?” The lead can select more than one option: HVAC, Plumbing, Electrical or Carpentry. Each service has its own team and its own follow-up steps.

router-3-real-example.gif — Home services form with HVAC, Plumbing, Electrical and Carpentry choices.

Example form where a lead can select more than one service.

  • Trigger: Form Submitted, for the home services form.

  • Action: Router with four branches.

  • Branch 1: Custom rules. The service includes HVAC.

  • Branch 2: Custom rules. The service includes Plumbing.

  • Branch 3: Custom rules. The service includes Electrical.

  • Branch 4: Fallback, for leads that match no other branch.

  • Inside each branch: the next steps for that team, such as a note, an internal notification, a tag or a task.

  • Result: a lead who selects HVAC, Plumbing and Electrical goes into Branch 1, Branch 2 and Branch 3, in that order. With If/Else, only the HVAC branch would run.

Frequently Asked Questions

Q: What is the difference between Router and If/Else?

If/Else sends the contact into the first branch that matches and ignores the rest. Router sends the contact into every branch that matches, one after another, from left to right.

Q: In what order do the branches run?

From left to right, in the order of the Branches list. Drag a branch to the top of the list to make it run first.

Q: Do the matching branches run at the same time?

No. They run one after another.

Q: How do I make a branch run for every contact?

Set its Branch Type to Always run. It runs for every contact, with no conditions.

Q: How do I handle contacts that match no branch?

Add a branch with the Branch Type set to Fallback. It runs only when no other path matched.

Q: How can I check which branches a contact will go into?

Open Test workflow, select the trigger and a real event, then click Start test run. After the test finishes, select the Router step on the canvas and open Output to review the matching branch conditions and their results.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article