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

If Else Workflow Automation: Yes/No Paths with Branch

FlowMattic Branch module: a WooCommerce order is checked against a total over 200 and sent to a Slack Yes path or an email No path.

If else workflow automation is the most common decision in any process: if a condition is true, do one thing, otherwise do something else. In FlowMattic, the Branch module handles it. It checks your conditions once and sends the run down a Yes path or a No path, each with its own chain of steps.

Branch suits every builder who needs two outcomes from one event: a VIP order and a normal order, a new customer and a returning one, an AI answer that is positive or negative. You see both paths on the canvas, so the logic reads like the sentence you would use to explain it.

What is the Branch module?

Branch by FlowMattic is a built-in step in the Flow Controls group of the app picker. It has a single action event, Evaluate Condition, which FlowMattic selects for you: “Evaluate a condition and determine Yes/No path to execute”.

On the canvas, a Branch node reads “Split by Yes/No condition” until you rename it, and two path markers sit under it: Yes and No. You add steps under each one, just as you would in the main chain. Branch is one of several workflow logic modules that share the same condition builder.

How if else workflow automation works with Branch

  1. Add a step and choose Branch by FlowMattic. The node appears with its Yes and No paths.
  2. Click the Branch node. Its settings open straight on the Conditions tab, with the note: “This action will automatically execute the Path “Yes” if the conditions are met, and “No” if the conditions are not met.”
  3. Build the condition: Choose field (a dynamic tag), Choose condition and Enter or select value. Click AND to add a condition to the group, or OR to start another group.
  4. Add steps under the Yes path and under the No path.
  5. Use the Test tab to see which path your sample data would take.
FlowMattic Branch step with Yes and No paths, each leading to a WP Tables step
A Branch on the canvas: runs that match the condition take the Yes path, every other run takes the No path, and each path has its own WP Tables step.

The condition builder is the same one the Filter uses: 32 conditions covering text, numbers, dates, booleans, presence (Exists, Is empty, Is blank) and format checks (Is Valid Email Format, Is Valid JSON, Is Valid URL Format, Is Numeric). All conditions in a group must match, and the Branch takes Yes when any group matches.

What a Branch gives the steps after it

OutputWhat it holds
path_to_executeyes or no: the path the run took
condition_mettrue when the conditions matched, false when they didn’t

Task History logs each decision in words: “Conditions meet. Executing Yes path.” or “Conditions does not meet. Executing No path.”, with the conditions it checked as the step’s input. When a run goes the wrong way, that entry tells you which value tipped it.

Use cases

Give big orders the white-glove treatment

Orders above a threshold get a personal touch, everything else gets the standard confirmation.

WooCommerce new order → Branch (total Greater than 200) → Yes: Slack message to the account team / No: Send Template Email confirmation

Separate staff sign-ups from customer sign-ups

Staff accounts don’t belong in your marketing list. A Branch on the email domain sends them somewhere else.

WordPress New User → Branch (email Ends with @acme.com) → Yes: Slack message to IT / No: FluentCRM contact with the welcome tag

Route refund requests to a person

A support form gets many kinds of questions. Anything mentioning a refund goes to a human, the rest gets an instant answer.

Form submission → Branch (message Contains refund) → Yes: Fluent Support ticket for the billing team / No: Send Email with help-centre links

Escalate negative feedback found by AI

An AI Agent labels each review as positive or negative. Branch acts on the label.

Webhook (new review) → AI Agent (answer positive or negative) → Branch (answer Exactly matches negative) → Yes: Slack alert to support / No: Google Sheets row

Onboard trial and paid customers differently

A SaaS product receives one webhook for every new account. The plan field decides which onboarding sequence starts.

Webhook (new account) → Branch (plan Exactly matches trial) → Yes: Mailchimp trial audience / No: HubSpot contact plus a Slack note to customer success

Watch a client site for agencies

An agency checks each client endpoint on a schedule and only wakes someone up when the check fails.

Schedule (every 15 minutes) → API request → Branch (status code Equal to 200) → Yes: WP Tables row "up" / No: Send Email to the on-call address

Tips and gotchas

  • Without a Join, each path is the end. When the Yes or No path finishes, the run ends there. To run shared steps afterwards, such as a CRM update, add a Join to bring the paths back together.
  • No conditions means No. A Branch with no conditions evaluates as No and continues down the No path.
  • Rename the paths. Yes and No can carry your own labels (“VIP”, “Standard”). A Join records the renamed label as the route that ran.
  • Nest when you need a second decision. A Branch can sit inside a Router route or inside another Branch path, and Branch works inside an Iterator loop.
  • The condition rules match the Filter’s. Text comparisons ignore case, number conditions compare whole numbers (decimals are dropped), and date conditions don’t match when a date can’t be read.
  • Map the decision later. Later steps can read path_to_execute from the Branch, which is useful in a summary email or a log row.

Related features

  • Router: more than two outcomes, each a named route with its own conditions.
  • Filter: when the No side should do nothing at all, stop the run instead of branching.

FAQ

When should I use Branch instead of a Router?

Use Branch when the decision is a plain yes or no. Use a Router when you need several named paths, each with different conditions. A Branch is quicker to set up because its No path needs no conditions of its own.

Can both paths of a Branch run in the same run?

No. The Branch evaluates its conditions once and runs either the Yes path or the No path. If you need steps that run after either path, add a Join after the paths.

How do I build if, else if, else logic?

Put a second Branch on the No path of the first one. For three or more outcomes that depend on the same field, a Router with one route per outcome is usually easier to read.

Branch is part of every FlowMattic plan, with unlimited workflows and runs on your own server. Try FlowMattic on a live demo site and build your first if else workflow automation in a few minutes.

More from the blog