Conditions: running only when it matters

Conditions are optional filters. When present, the automation only continues if they're met. They keep an automation from firing in situations you didn't intend.

How to read a condition: field → operator → value. For example: Amount → greater than → 5000.

Available operators:

• equals / does not equal

• contains — the value appears somewhere in the field

• greater than / greater than or equal

• less than / less than or equal

• is empty / is not empty

• changed to — the field just became this value (great with "status changed" triggers)

When a condition isn't met, you choose what happens:

• Stop the automation (nothing else runs), or

• Skip to the end (skip the remaining steps but finish cleanly).

Examples

• Invoice created → only if amount greater than 5000 → notify the owner.

• Project status changed → only if status changed to "On Hold" → email the client.

• Form submitted → only if the "Budget" answer is not empty → create a lead task.

Tip — start broad, then tighten. Build without conditions first and watch what runs (using the run history). If it fires too often, add a condition to narrow it. It's easier to tighten a working automation than to debug an over-filtered one that never runs.