tr Skip to content
Black Friday FlowMattic for life, 12 payments of $33.25 Or $399 once. Nothing added for splitting Ends in --Days --Hrs --Min --Sec See the deal

Conditional Workflow Routing with the FlowMattic Router Module

FlowMattic Router module: a new order is split into a high-value route to Slack and a standard route to email, then a Join leads both into a CRM step.

Conditional workflow routing sends each run down the path that fits it: a large order one way, a small order another, a VIP customer somewhere else again. In FlowMattic, the Router module does this on the canvas. It splits a workflow into named routes, each with its own conditions and its own chain of steps.

Use it whenever one event needs more than one kind of handling. Store owners route orders by value or country, agencies route leads by service, support teams route tickets by topic, and AI workflows route on an agent’s answer.

What is the Router?

Router by FlowMattic is a built-in action with one event, Conditionally run…. On the canvas it appears as a step labelled “Split tasks by conditions”, with routes fanning out below it. Each route has three parts:

  • A route label, such as Route A, which you can rename to something meaningful like “Orders over 500”.
  • A Route Conditions step that decides whether the route runs.
  • The steps that run when it does.

It sits alongside the other logic modules: Filter stops a run, Branch takes a yes or no path, and Join Paths brings routes back together.

How conditional workflow routing works

  1. Click + after a step and choose Router. The builder adds the Router with two routes, Route A and Route B.
  2. Open a route’s Route Conditions step. Choose a field from the trigger or an earlier step, pick an operator and enter a value. Use AND to add a condition that must also be true, and OR to start a new group that can be true instead.
  3. Add steps under the route with the + below its conditions.
  4. Click the + at the end of the route row to add Route C, D and so on.
  5. Use a route’s menu to Rename, Duplicate, Manage Notes or Delete it. Duplicate copies the route with its steps.
  6. To check the routes before you save, click the Router’s test button, Test routes with sample data. It opens the data captured above the Router, ready to edit. Click Test and each route shows Runs or Skipped, with every condition and the value it compared; a condition that reads nothing from the run is marked as fixed text. Nothing is saved or sent.
  7. To continue with shared steps after the routes, add a Join Paths step where they should meet.
FlowMattic visual builder showing a webhook trigger, a Router, and two routes, Orders over $500 and All other orders, each starting with a Filter conditions step followed by an Email step, with Route A's conditions open.
A Router with two routes, each starting with its own conditions step: orders over $500 email the sales lead, all other orders get the receipt. Route A's conditions are open on the right.

What happens during a run

Routes are checked in order, Route A first. When a route’s conditions are met, its steps run, and then the next route is checked. When they are not met, the route is skipped and the next one is checked. Every route whose conditions match runs, so a run can take more than one route.

Task History records each decision as “Route Condition: route name“, with “Conditions meet. This route will be executed.” or a note that the route was skipped, plus the conditions that were evaluated. You can always see why a run went where it did.

Condition operators

TypeOperators
TextContains, Does not contain, Exactly matches, Does not exactly match, Is in, Is not in, Starts with, Does not start with, Ends with, Does not end with
NumberGreater than, Less than, Equal to, Not equal to, Greater than or equal to, Less than or equal to
Date/timeAfter, Before, Equals, Does not equal
BooleanIs true, Is false
PresenceExists, Does not exist, Is empty, Is not empty, Is blank, Is not blank
FormatIs Valid Email Format, Is Valid JSON, Is Valid URL Format, Is Numeric

Is in takes a comma-separated list of values. Presence and format operators need no value.

Use cases

Orders handled by value

Orders of 500 or more alert the team in Slack and get a personal thank-you email; smaller orders get the standard confirmation. A Join brings both back for the CRM update.

New Order Created → Router (total ≥ 500 | total < 500) → Slack · Email → Join Paths → FluentCRM

Support tickets routed on an AI label

An AI Agent labels each message billing, bug or question. Each label has its own route: billing to the finance inbox, bugs to the issue tracker, questions to the help channel.

Email Received → AI Agent → Router (label exactly matches …) → Email · Webhook · Slack

Agency leads sent to the right specialist

A form asks which service a prospect needs. Routes for SEO, design and development each notify a different person and add a matching CRM tag.

Form Builder submission → Router (service) → Slack · FluentCRM

Shipping rules by country

A Router uses Is in with a list of country codes. Domestic orders go to the local fulfilment sheet, EU orders to the EU partner’s webhook, and everything else to manual review.

Order Paid → Router (country is in … | is not in …) → Google Sheets · Webhook · Email

SaaS sign-ups handled by plan

A webhook from the billing system carries the plan name. Free sign-ups get the onboarding email series; paid plans also get a welcome call booked by the account team.

Webhook → Router (plan) → Send Template Email · Slack

Comments moderated three ways

An AI Agent scores each comment. Clean comments are approved, doubtful ones go to a person, and spam is deleted.

New Comment → AI Agent → Router → Update Comment · Slack · Delete Comment

Data checks before a CRM sync

Internal ops teams use the format operators as a gate. A route with Is Valid Email Format adds the contact; a route with the opposite check logs the bad record in WP Tables for a person to fix.

Webhook → Router (email is valid | email does not contain @) → FluentCRM · WP Tables

Tips and gotchas

These come from how the Router evaluates routes, and they save a lot of head-scratching in conditional workflow routing:

  • Make routes exclusive if only one should run. Every matching route runs. If an order can match both “over 500” and “VIP”, both routes will run unless the conditions rule each other out.
  • A route with no conditions is skipped. There is no automatic catch-all route. For an “everything else” path, give the last route conditions that are the opposite of the others.
  • Text comparisons ignore case. Route conditions use the same checks as the Filter, which lowercase both the field and the value first, so “Acme” Exactly matches “acme”.
  • Add a Join for shared steps. Without Join Paths, the routes are the end of the workflow. With it, the steps after the Join run once, whichever routes ran.
  • Name your routes. The route name appears in Task History, so “Orders over 500” is far easier to debug than “Route A”.
  • Delays inside a route are fine. A route that ends with a Delay, or whose conditions don’t match, no longer stops the routes after it from being checked.
  • One decision only? Use Branch for a plain yes or no, or Filter to stop runs you don’t want at all.

Related features

  • Join: bring routes back together so the shared steps run once.
  • Branch: a single yes or no decision with two paths.
  • Filter: continue or stop a run on a condition.

See how every logic module fits together on the workflow logic page.

FAQ

What is the difference between a Router and a Branch?

A Branch evaluates one condition and takes the yes path or the no path. A Router has as many named routes as you add, each with its own conditions, and every route whose conditions match runs.

Can more than one route run?

Yes. Routes are checked in order and each matching route runs its steps before the next route is checked. To get exactly one path, write conditions that cannot be true at the same time.

Is there a default or fallback route?

Not automatically: a route without conditions is skipped. Create a last route whose conditions are the opposite of the others, for example “country is not in” the list your other routes use.

Can I put a Router inside a route?

Yes. A route can contain another Router or a Branch when a decision has a second level. If the nested decision should meet the outer path again, give it its own Join first.

How do I see which route a run took?

Open the run in Task History. Each route has a “Route Condition” entry that says whether it ran or was skipped, along with the conditions that were checked.

Build the decision once and let every run find its own way. See FlowMattic pricing and add a Router to your next workflow.

More from the blog