Conditions and switch routing

Use a Condition node for a yes/no decision. Use a Switch node when one value needs several named routes plus a default.

Field-based conditions

Select the payload or a supported Magento condition model, then choose a field, comparison and value. The builder presents known fields for the selected model. A saved card shows the concise rule, which makes a final visual review worthwhile.

For a high-value order, a condition can compare the event entity's grand total with the approval threshold. Connect YES to the approval task. The NO branch may go to a named End node, or remain unconnected when stopping at the condition is the intended result.

Expression conditions

Expression mode evaluates a rule against the current payload. It is useful when the decision spans nested values or cannot be expressed by one field comparison. Expressions run only while the Expression Engine setting is enabled.

Keep an expression small and use payload keys that the trigger actually supplies. For example:

payload["entity"]["grand_total"] > 500

A missing key is not the same as a value of zero. Simulate both the matching and non-matching path when optional event data is involved.

Switch routing

A Switch node evaluates one value against its configured cases. Each case becomes a connection port, and the default port catches values that did not match. Case labels should be stable identifiers rather than display prose because connections depend on them.

Practical routing review

Test each reachable branch, including the default or NO path. A simulation that proves only the happy path can still leave a disconnected rejection, fallback or low-value route. When business rules overlap, document which condition runs first; the graph order is the rule order.