Flow control

Conditional Block

Conditional evaluates a switch value, checks cases in order, and follows the first matching branch or the default branch.

At a glance

Best for
Branching logic
Operators
General, number, and text comparisons
Output
Optional evaluated text
Error handle
Yes

What it does

Conditional lets one Flow path split into different branches. It evaluates a configured switch expression and compares it with ordered cases.

The first matching case wins. If no case matches, the default path runs.

Number operators only match when both values resolve to valid numbers. They never compare text alphabetically.

Use it when

  • Handle empty versus non-empty extraction results.
  • Route by status text, category, price, or page state.
  • Use a fallback path when a value does not match expected cases.

Do not use it when

  • Every branch should run; use separate connected paths instead.
  • You need repeated iteration; use Loop.
  • The switch value has not been created before this Block runs.

Settings

Conditional needs a switch expression and one or more cases. Cases are checked top-to-bottom.

Switch value

Required: Yes
Variables
Yes
Description
Value to test. Use variables or literal text.

Cases

Required: Yes
Variables
Case values can use variables
Description
Ordered conditions using Is, Is not, number comparisons, or text comparisons.

Default path

Required: No
Variables
No
Description
Path followed when no case matches.

Output variable

Required: No
Variables
Variable name
Description
Stores the evaluated switch value when configured.

Outputs

Conditional can save the evaluated switch value.

{{outputVariableName}}text

The evaluated value, when an output variable is configured.

matchedCasestring

Runtime result describing which case matched.

Example Flow

Use Conditional after extraction or calculation when the next step depends on the value.

  1. Create or extract a value.
  2. Evaluate it with Conditional.
  3. Run the matching branch or default branch.

Errors and fixes

Start with symptoms visible in the editor or Inspector, then check the earliest Block that produced the wrong page state, variable, or output.

The wrong branch runs.

Check
Check case order and the exact evaluated switch value.
Fix
Move the most specific cases higher or adjust the operator.

No case matches.

Check
Inspect the switch value in Inspector mode.
Fix
Add a matching case or connect the default path.

A number comparison never matches.

Check
Check whether both the value to check and the case value resolve to plain numbers.
Fix
Convert extracted price or count text to a Number before comparing it.

Local and cloud runs

Local runs and Cloud Runs use the same case order, operators, variable interpolation, and strict number-comparison rules.