Skip to main content
Conditions evaluate context data and branch execution into true/false paths. This condition evaluates runtime data and routes execution based on whether the configured logic matches.

​
When To Use

  • Escalate only when multiple risk signals are all present.
  • Allow progression when any one of several prerequisites is met.

​
Configuration Checklist

  1. Add multiple rules inside one logical group.
  2. Choose group logic (AND or OR).
  3. Nest groups if you need more complex expressions.
  4. Test with representative payload combinations.

​
Inputs

  • node.data metadata (uiId, componentId) and condition-specific operands/operators.
  • Context values from trigger/action outputs to evaluate.
  • Optional array/object inputs depending on the condition type.

​
Outputs

  • Routes execution through true and false branches.
  • Optionally emits evaluation details for debugging (implementation-dependent).
  • Determines which downstream path executes next.

​
Failure Modes

  • Missing operand values or invalid operator selection.
  • Data type mismatches (for example string vs number vs date).
  • Misconfigured complex expressions (switch/logical group cases).
  • Unconnected branches creating dead-end workflow paths.

​
Best Practices

  • Connect this where branching is required and make sure downstream edges use true/false handles.
  • Always wire both branches to avoid dead ends in production runs.