Narrow a trigger with conditions
A workflow that runs on everything is slow, noisy, and hard to trust. Most of the time you only care about some records — invoices over a limit, or from one supplier, or in one currency.
- A walkthrough video, then the six steps to add one
- The five operators you get, and the one you will miss
- How to test who created the record
- Why a record that does not pass leaves no trace at all
01 · Video
Feature walkthrough
02 · How
Add a condition
- Open the trigger.
- Choose the table first. The
Conditions (optional)block only appears afterwards. - Press
Add Condition. - Pick a field.
- Pick how to compare it:
Equals,Not Equals,Contains,Greater Than,Less Than. - Type the value.
Add more conditions and they all have to be true. To remove one, press the bin on its row.
03 · Expected result
The workflow now runs only on records that pass. Everything else is ignored, quietly — nothing is recorded for records that did not match, and nothing appears in the logs.
04 · Troubleshooting and notes
There is no "is empty" here
The five operators above are all you get in a trigger condition. If what you actually want is "the PO number is missing", you cannot do it at this stage — add an If / Or step instead, which does have is empty. See Check something before you act.
You can also test who created the record
Switch the field picker from Record to Creator and you get the person’s email, name, job title, department, workspace role and more. That is how you write "only invoices entered by the Finance team".
Match status is in the field list too
Under a Match group at the top, so you can filter on it without using the match-status trigger.
05 · FAQ
Common questions
Before. If the record does not pass, the workflow never starts, and nothing appears in the logs.
Not in trigger conditions — they are all ANDed. For OR, use an If / Or step.
Not here. The If / Or step can.