Showing results for 
Search instead for 
Did you mean: 

Create a trigger for SharePoint list columns

It would be nice to have a trigger if a certain column in a SharePoint list is modified. For example, if the column "Status" is modified, or if the column "Assigned To" is populated. So we don't have to use the trigger "When an item is created or modified", where you have to create a lot of workaround conditions just to make sure that the column that was updated is what you need. 

Status: Completed

Hi all,


Happy to update that this feature is now rolled out to and available for use. The documentation is updated as well:

For more info about how to use this action, see this tutorial: Introducing 'when an item or file modified' trigger and 'Get changes' action


Thank you all for the feedback and please let us know if you have any questions.





It should be possible to just trigger a flow when a specific field is changed in a sharepoint list

Regular Visitor

Help!! we really need this functions ASAP!!  Can you give me an opportunity to test it!!

Regular Visitor

Please yes and thank you.  This is making me insane.

New Member

Our experience: Business Owner wants to send email (contains file properties and attachement) to other departments when file is created in SharePoint library. Currently, no custom properties are shown in the email, since file is first uploaded, then flow trigerrs and only then custom properties can be added by user. This feature request would solve above problem, since email would be sent only when custom properties are added and be ready to share with others.

Regular Visitor

This would be an amazing additional feature

Advocate IV

Something like the "Before Properties" and "After Properties" known from Event Receiver Development would be helpful. For me it's OK, if the Flow starts at every Item Update, but it would be helpful to determine what has changed.



Kudo Kingpin

woiuld be very helpful, indeed !!!

New Member

Agreed!  Please add this feature.

Not applicable

It is embarrasing how basic functionality like "Item modified" and conditional triggers doesn't exist after all this time. It seems like there will be another 1-2 years before Flow is mature enough to be able to be used in an enterprise context.

Regular Visitor

This is a major usability issue as in its current state you have to do a lot of extra kung fu to prevent multiple flows triggering on the same list from creating an infinite loop (for instance if they update the list)

I think both the ideas in this thread are valuable-- Once the logic is there to have access to both the previous version of the list item and the new version of the list item, you can also create an easy to use trigger that just acts if a particular field is changed.

Right now this takes a handful of flow actions to make work, and I have to add extra fields to my list to manage the flow state. It makes it less usable to both the user and the developer. And while I was developing, I occasionally got into an infinite loop which can't be great for MS servers...