Skip to main content
The Condition node evaluates an expression and routes the workflow down one of two paths: True or False.

Configuration

Available operators

Output handles

The condition node has two output handles:
  • True: the workflow follows this path when the condition is met
  • False: the workflow follows this path when the condition is not met
Connect downstream nodes to one or both handles.

Branches that converge

If both the True and False branches eventually feed into the same downstream node, that node becomes an implicit merge point: it runs once, after whichever branch executed completes. This is how you run shared work “after either outcome” without duplicating the nodes on both sides.
Log outcome runs once, regardless of which branch the condition took. Same implicit-merge rule as Parallel: any node with two or more incoming connections is treated as a merge.

Examples

Check order value

  • Field: order.totalPrice
  • Operator: greater than
  • Value: 100

Check if field exists

  • Field: customer.email
  • Operator: is not empty

String matching

  • Field: order.status
  • Operator: equals
  • Value: fulfilled

Tips

  • You can chain multiple condition nodes for complex logic (e.g., if A, then check B).
  • Both the True and False branches are optional; you don’t need to connect both.
  • Use descriptive node labels like “Order > $100?” so the workflow reads naturally.