Condition node
A Condition node branches execution based on an expression. You set a left operand and an operator (equals, not_equals, greater_than, less_than, contains, is_empty, is_not_empty). For binary operators, set a right operand (it may be empty for equals / not_equals). For is_empty / is_not_empty, the right side is not used. For dynamic values, use workflow references such as $trigger.<triggerId>.<fieldKey> or $task.<taskId>.outputs.<fieldKey> on the left or right. Connect the Yes branch when the condition is true and the No branch when it is false; you can use both or just one.
Loop node
A Loop node repeats a task multiple times. Set max iterations (1–20), optionally a delay between iterations (0–60000 ms), and connect the loop start task that runs on each iteration. Use loops when you need to repeat the same step (e.g. with data from the previous run or a counter).
Parallel node
A Parallel node runs multiple branch tasks at the same time. Add one or more tasks as branches; they all run concurrently. The workflow continues from the configured next step after all branches complete. Use parallel nodes for independent steps that do not depend on each other.
Best practices
- Always connect both Yes and No on condition nodes when possible (even if one path is intentionally empty) to avoid warnings and unclear behavior.
- Set loop max iterations and connect the loop task so the node is fully configured.
- For more on passing data into conditions and tasks, see Input Mapping and Workflow References.