Conditions: simple If and Switch (branch) with AND/OR

The difference between the If (single rule) node and the Switch (multiple branches) node, and how to combine rules with AND/OR.

Jun 26, 2026

Watch this step in the video · If condition: a single rule

What they are and when to use them

Conditions let a workflow make decisions. Omnifox has two nodes for this, both in the Conditions section of the palette:

  • If (single rule) (if): evaluates one comparison and splits the flow into two outputs: True (matched) and False (not matched).
  • Switch (multiple branches) (branch): allows several branches, each with several rules combined with AND/OR. Branches are evaluated in order and the first one that passes wins; if none match, it exits through Default.

Use If when there are only two paths (for example "is the country Ecuador?"). Use Switch when there are three or more outcomes or you need to combine conditions.

Steps for the If node

  1. In the Workflows editor, drag the If (single rule) node onto the canvas.
  2. In the inspector choose the Field (a trigger variable or a variable defined earlier, such as $email).
  3. Choose the Operator. Depending on the field type you'll see options like equals, not equals, contains, starts with, is empty, is not empty, greater than, less than.
  4. If the operator needs it, type the Value. It supports {{$variable}} to compare against another variable.
  5. Connect the True and False outputs to the following nodes.

Steps for the Switch node with AND/OR

  1. Drag the Switch (multiple branches) node onto the canvas.
  2. For each branch, give it a name (it becomes the output label) and pick the connector AND (all rules must match) or OR (any rule is enough).
  3. Add the branch's rules: field, operator and value, just like in the If node.
  4. Add more branches for more paths. Order matters: the first one that matches wins, the rest are skipped.
  5. Connect each branch and the Default output (when none match) to their nodes.

Verification

Run a test with real data and check the workflow's run history: you'll see which output it took each time. If a branch never fires, it's usually because of the order or because an earlier rule shadows it.

If it doesn't work

  • Always exits through False/Default: check that the Field actually exists at that point in the flow. Comparing a variable that wasn't defined yet returns empty.
  • The operator is missing: the operator list depends on the field type. Change the field, then pick the operator again.
  • A Switch branch never evaluates: it sits after another branch that already matches. Reorder the branches (first match wins).

Tips

  • Keep rules simple: if a branch grows huge, split it into two branches or use a second Switch.
  • Renaming a branch doesn't break existing connections: the output is identified by its internal id.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp