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

  • Enforce that production resources carry mandatory tags.
  • Route to different teams based on ownership tag presence.

​
Configuration Checklist

  1. Set the target resource identifier.
  2. Choose check mode (any tags, key exists, key/value, tag count).
  3. Configure mode-specific fields.
  4. Branch based on tag policy compliance.

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