The Condition node

The Condition node branches a CloudRadial AutomationAI workflow on a set of rules. It evaluates each rule and sends the flow down its true branch or its false branch, letting you build if/else logic. This article is for workspace users with the Admin role or higher who build workflows in the Designer.

• Match: All vs. Any
• Writing Rules
• Operators
• Wiring the Branches

Match: All vs. Any

Add a Condition node from the Logic section of the palette. A Condition holds one or more rules and a match mode that decides how they combine:

• All rules (AND) — the condition is true only when every rule is true (the default)
• Any rule (OR) — the condition is true when at least one rule is true

Writing Rules

Each rule has three parts:

• left — the value to test, typically a binding expression that reads an earlier node's output
• operator — how the two sides are compared
• right — the value to compare against (omitted for the unary operators below)

Operators

The Condition node supports these operators:

• equals — the two sides are equal
• notEquals — the two sides are not equal
• gt — left is greater than right
• lt — left is less than right
• gte — left is greater than or equal to right
• lte — left is less than or equal to right
• contains — left contains right (substring of a string, or membership in a list)
• isEmpty — left is null, an empty string, or an empty collection (takes no right side)
• isTruthy — left is present and not false, zero, or empty (takes no right side)

The isEmpty and isTruthy operators are unary: they test the left side alone, so no right value is used.

Wiring the Branches

The Condition node has two output branches, true and false. Connect each branch to the node that should run next for that outcome. The Condition is evaluated in the control plane rather than on a runner, so it has no timeout or retry fields and adds no runner step. Either branch can lead on to more nodes or to an End node.