A simple way to create a trigger condition in Power Automate
“I’d like to save flow runs by adding a trigger condition to my Power Automate flow but I don’t know what the actual condition should look like.”
Trigger condition is the solution for a few Power Automate problems. The infinite trigger loop is the biggest one, but it can solve even the small problems, e.g. if your flow is running too often.
If you use a trigger ‘.. is modified’, your flow will trigger with each update. But you probably don’t want the flow to do something on each update. Most of the flow runs will do nothing, they’ll just consume a flow run while waiting for a specific update. And that’s where you can use a trigger condition, if you know how to build one.
Use ‘Filter array’ to create the trigger condition
The simplest way to build a trigger condition I found is to use the ‘Filter array’ action. The action itself is designed to do something completely different, but it offers a nice feature. You can build a condition using the ‘Filter array’ interface and then convert it into an expression with the ‘advanced mode’.
Let’s take an example: a trigger condition to trigger a flow only if choice column ‘ApprovalStatus’ has value ‘Not started’. Add the ‘Filter array’ action into your flow and enter the condition.
Then click on the ‘Edit in advanced mode’, the action will convert the condition into an expression.
An expression that you can copy and use as the trigger condition. Once you add the trigger condition, you can remove the ‘Filter array’ action.
Combine the trigger conditions
AND
All the trigger conditions on all the lines must return ‘true’ for the flow to trigger. If you need multiple conditions, repeat the same process for each of them and place them on separate lines. The example below will trigger the flow only if ‘ApprovalStatus’ value is ‘Not started’ AND ‘Approver’ is empty.
OR
It gets a bit more complicated when using OR in the trigger condition. As mentioned above, the lines have AND relation between them. If you need OR you must put everything on a single line. You can still use the ‘Filter array’ action to build the conditions, but you can’t use it directly. You must add the OR condition manually to connect the pieces.
@or(condition1, condition2, condition3,...)Note: you must remove the @ from the conditions, @ should be only at the beginning.
Using the condition from the example above, ‘ApprovalStatus’ value is ‘Not started’ OR ‘Approver’ is empty.
@or(equals(triggerOutputs()?['body/ApprovalStatus/Value'], 'Not started'),equals(triggerOutputs()?['body/Approver'], null))
Summary
The trigger conditions might look confusing when you see them for the first time. There’s no dynamic content available, no expressions, it’s just a free text field. But it’s a free text field expecting that you’ll know how to create the trigger condition.
Luckily, like many times before, there’s a way to make your Power Automate life easier. You don’t need to search for the column internal name or for a specific expression, ‘Filter array’ action will do it for you. Create the condition in the user interface, switch to advanced mode, and take it from there.
This post described only the trigger conditions where you’ve got empty/fixed value in a column, but you can use similar trigger conditions also to start a flow on a change in a specific SharePoint column.
Thank You for Your post!
What to do when I interested in a free text field change? There is no predefined status to look for, it is just a text box where the users add updates. I wouldn’t start the flow for each modification, just when that given field has changed. Using Your method, I received this:
“@equals(outputs(‘Get_changes_for_an_item_or_a_file_(properties_only)’)?[‘body/ColumnHasChanged/Requisition_x0020_Notes’], true)”
Hello Sebastian,
to monitor changes in a free text field you’ll need a ‘backup’ column, one extra column where you’ll store the original value and compare it with the ‘main’ free text column on every change. I already wrote a post on this that I believe will explain the solution in more detail: https://tomriha.com/how-to-trigger-power-automate-flow-on-specific-sharepoint-column-update/.
Hello very interesting these points!
How would a trigger of this type be for an Azure trigger, that is when a work item is updated with the status = CAB Submitted, and the field Crtl Verification = Submitted?
And subsequently prevent this from running infinitely?
Thank you very much in advance.
Hello Amaury,
I didn’t work with Azure triggers so I don’t know if it’s done differently than this.
Great sharing! This helped me to resolved my issue that I only want my approval flow trigger while the stage & status under specific value and update the stage & status to another value after approval. Thanks for sharing such great solution 🙂
This solution was super simple and worked perfectly, thank you!
Once I read this section of the page, https://docs.microsoft.com/en-us/power-automate/triggers-introduction#customize-a-trigger-by-adding-conditions , I was concerned. I’m preparing to teach Power Platform to users in a large, global company, and this seemed important! That link didn’t work until I changed the https to http. Meanwhile, I found your article here. Then I reached that other article and it was super complex! I’ve recommended this article as a replacement for it in my feedback suggestion.
I would love to hear your thoughts on triggering a flow based on a choice field with multiple selections. Basically, I have a field where people can choose more than one option: Red, Green, Blue. I want the flow to trigger if Red is one of those choices. I cannot figure out how to make that work, even when I use the filter array to build the expression. Any advice is appreciated!
Hello Nikki,
my thoughts on this are in the new post, I hope it helps.
The same thing happens to me, I would like to know how to execute a flow depending on a column of options in my case my column of options is quite simple with a YES or NO, but because I do the step of filtering the matrix I cannot make it activate :(, you could find the way?
Hello Esteban,
I wrote a new post regarding multiple choice columns, but in your case it sounds like a single choice column. In that situation you just need to use the ‘Column Value’ dynamic content when building the condition in the ‘Filter array’ action.