GoHighLevel Router Workflow Action: Run Every Matching Branch, Not Just the First

Short answer: Router is a new GoHighLevel workflow action (Official, HighLevel changelog, October 29, 2026) that sends one contact down every branch it matches, not just the first one. If/Else stops at the first match; Router checks all branches and runs each matching one in order, left to right. Branches can be Custom rules, Always run or Fallback (runs only when nothing else matched). Add it from Automation, Workflows, set the branches and test it on a real event. HighLevel has not announced any extra cost or branch limit.

What the Router action does

Most GoHighLevel builders have hit this problem: a lead ticks two or three options on a form, and the If/Else action only follows the first branch that matches. The usual fix was a second or third workflow, or a chain of If/Else steps, and both get hard to maintain.

Router removes that workaround. According to the changelog (Official), it evaluates every branch for the contact and runs each one that passes, one after another, in the order you set. There are three branch types:

• Custom rules: runs only when its conditions match. You set them under "Only continue if" using any field, an operator, and more conditions or rule groups if needed.
• Always run: runs for every contact that reaches the Router, with no conditions.
• Fallback: runs only when no other branch matched, so nobody falls through the cracks.

The changelog gives no maximum number of branches; it says you can add as many as the use case needs.

Router vs If/Else: which one to use

• Use If/Else when the paths are mutually exclusive: a lead is either in your service area or not, a deal is either won or lost. One answer, one path.
• Use Router when a contact can qualify for several things at once: multiple services, several interests, more than one team that needs to know, or a step that should always run alongside the conditional ones.
• Use Router with a Fallback when you need a guaranteed catch-all, such as an internal task for a person to review leads that matched nothing.

One detail matters for timing: branches run sequentially, not at the same time. If Branch 1 has a long wait step, think about whether Branch 2 should run first, and drag the branches into the order you want.

How to set up a Router

1. Go to Automation, then Workflows, and open the workflow.
2. Add the Router action where the paths should split.
3. Open the first branch and choose its type: Custom rules, Always run or Fallback.
4. For Custom rules, set the conditions under "Only continue if".
5. Click Add branch for each additional path.
6. Optionally drag branches in the Branches list to set the run order.
7. Add the actions inside each branch: tags, notes, internal notifications, tasks, messages or opportunity updates.
8. Save the action and use Test workflow on a real event. The test output shows each branch as passed or not, with the reason and the contact's actual value.
9. Save and publish the workflow.

Example: a home services lead form

HighLevel's own example (Official) fits most trades businesses. A form asks "What service do you need?" with HVAC, Plumbing and Electrical options. The Router has a branch for each service plus a Fallback. A lead who picks all three passes Branches 1, 2 and 3, so each team gets its own note, notification, tag or task from a single workflow. A lead who picks none of them lands in the Fallback.

The same pattern works for a med spa (several treatments of interest), a law firm (more than one practice area) or an agency (several services on an inquiry form).

Mistakes to avoid

• Double messages: if two matching branches each send an SMS, the contact gets two texts. Put customer-facing messages in one place, often an Always run branch, and keep the service branches for internal steps.
• Overlapping workflows: once one Router replaces several duplicate workflows, turn the old ones off so contacts are not enrolled twice.
• Forgetting the Fallback: without it, a contact that matches nothing simply skips the Router. Add one for anything that needs a human.
• Testing on real customers: test runs execute real actions, so use your own contact.

Other workflow releases from the same day

The Router shipped alongside several other workflow updates on October 29 (all Official): Skills in the AI Agent Action (reusable instructions the agent loads only when needed, with four built-in skills), Web search as a built-in AI Agent tool (billed at 1 cent per search on OpenAI and Claude models, 1.4 cents on Gemini), testing inside AI Builder (Labs toggle "The New Test Workflow"), and the AI Video Generation and AI Analyze Video actions. See our guide to GoHighLevel AI Video Generation and the full list on our LevelUp 2026 announcements hub. If you split traffic to compare messages, our workflow A/B testing guide covers that action.

What to do now

List the workflows you duplicated only to handle a second match, and the If/Else chains that are getting long. Those are your first Router candidates. If your account has grown messy and you want someone to map and clean it up, see our GoHighLevel account audit or ongoing GHL care plan, or book a free discovery call.

Yaakov (Koby) Oranski, Founder and CEO of Yotomations

Certified GoHighLevel Admin and Partner. Koby designs CRM migrations, two-way integrations, billing systems and AI agents for service businesses, and writes from the engagements described on this site.

Published 2026-10-30