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

  • Proceed only when affected-sites list is non-empty.
  • Branch when required tags are missing from an array.

​
Configuration Checklist

  1. Set input array path.
  2. Choose array operator (contains, empty, length checks, etc.).
  3. Configure operator-specific values.
  4. Use branches to handle empty vs non-empty outcomes.

​
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.