Multi Condition Node

The Multi condition node splits a workflow into more than two paths. Use it when subscribers should take one of several mutually exclusive branches, instead of chaining True/False Condition nodes.

A Multi condition node evaluates named branches from top to bottom. Each branch has its own tag conditions. The first branch whose conditions all match wins. If none match, the subscriber continues on the Else lane.

Use it for plan tiers, lifecycle stages, or any first-match routing where Condition (True/False) is too narrow.

[todo: Screenshot of a Multi condition node on the workflow canvas showing If 1, If 2, and Else lanes converging at a join]

When execution reaches the node, PushFire checks branch 1, then branch 2, and so on. Evaluation stops at the first match. Later branches are not evaluated for that subscriber.

Inside a single branch, every tag condition must match (AND). Across branches, order is first-match: the first matching branch wins. Put the most specific branches first so they are not shadowed by a broader rule above them.

[todo: Screenshot of ordered If branches on the canvas with badges (If 1, If 2) and the Else badge]

Condition: two paths only (True and False). Best for a single yes/no check.

Multi condition: three or more outcomes, including Else. Best for first-match routing across several tag sets.

Label

Required. Name the split for the canvas, for example Route by plan instead of the default Multi condition.

Description

Optional. Record why the split exists and which branch should win when tags overlap.

Branches

You need at least one If branch. Use Add branch condition for each extra outcome. For every branch:

• Branch name: optional label shown on the lane (for example Premium). If empty, the canvas still shows If 1, If 2, and so on.
• Tag conditions: all conditions in that branch must match. Choose a tag, operator, and value the same way as on a Condition node.

The Else row is always present and is not editable as a condition. It runs when no If branch matches. You cannot remove Else; you can only remove extra If branches (at least one If must remain).

[todo: Screenshot of the Multi condition side panel: Label, Description, collapsed If cards with tag summaries, the Else row, and Add branch condition]

When you add a Multi condition node, PushFire creates a lane per If branch plus Else, and a join that brings those lanes back to a single path. You do not wire those connections by hand.

Add Wait, notifications, or Stop on any lane. Empty lanes still converge at the join so the graph stays valid.

[todo: Screenshot of Multi condition lanes with add-node controls on each branch and the automatic join below]

Plan or tier routing

Branch 1: plan equals enterprise. Branch 2: plan equals pro. Else: everyone else. Order enterprise before a looser paid rule if both could match.

Lifecycle messages

Send different onboarding, nurture, or win-back sequences from one split instead of nested Condition nodes.

Order branches by specificity. Narrow rules first.

Always design Else. Unmatched subscribers still continue; put a default message there or a Stop if they should leave the journey.

Keep AND inside a branch small. If you need many independent outcomes, add branches rather than one huge tag list.

Test every lane. Include a subscriber who should hit Else.

If everyone lands on Else, tags or values likely do not match (including letter casing). If everyone lands on the first branch, that branch is probably too broad or ordered too high.

A subscriber matching two branches still takes only the first one in the list. Reorder or tighten tags if that is unexpected.

• Nodes
• Condition Node
• Stop Node
• Workflows
• Tags