Skip to main content
condition is the thinnest predicate node — a single boolean expression with two outbound paths: true and false.

​
Configuration

{
  "id": "cnd-aml-score",
  "type": "condition",
  "data": {
    "label": "AML Score Check",
    "expression": "aml_aggregate.high_risk_count > 0",
    "trueLabel": "High risk found",
    "falseLabel": "Clear"
  }
}
FieldNotes
expressionBoolean expression evaluated against the run context.
trueLabel / falseLabelCanvas labels for the outbound handles.

​
Edges

Edges from a condition carry sourceHandle: "true" or sourceHandle: "false". 
{
  "id": "e-cond-pass",
  "source": "cnd-aml-score",
  "target": "act-block",
  "sourceHandle": "true"
}

​
When to use vs rule

conditionrule
OutcomesExactly twoMany, plus else clause
OutputNone (pure routing)Named output fields
Best forSingle yes/no gateMulti-outcome lookups
condition is a stripped-down convenience — every condition can be expressed as a rule with two conditions. The shorthand keeps the canvas readable on simple guards.