Conditions: when should a step run?

A Condition block checks one piece of the event's data (for example, the purchase order's net amount) and, depending on the result, continues the process on the Yes or the No branch. This way an action only runs when it really should.

Setup:

1. Drag a Condition block onto the canvas and connect it after the Trigger (or an earlier step).
2. Click it and fill in the panel on the right:
   • Field – which piece of the event's data to check (the fields on offer depend on the trigger),
   • Operator – for example =, !=, >, >=, <, <=, "contains", "in", "is empty",
   • Value – what to compare against.
3. Connect the Yes output to the step that should run when the condition holds, and the No output to the other case.

Examples:

• Request approval only for purchase orders above HUF 100,000; below that a notification is enough.
• Notify the buyer only for a specific supplier.
• Start a process only when an opportunity reaches a certain stage.

With the "in" operator you can list several values separated by commas.

On activation every Condition block must have both a Yes and a No branch; if one is missing, activation stops with an error message.