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: Started

Hi all,


Happy to announce that we started the development of building granular trigger for SharePoint item and file changes along with a new action to check if a particular column value was modified since the last flow run.


To support this, we will be releasing a new trigger and a new action that works along with this new trigger to help you get started. 


  1. 'When an item or file is modified' trigger
    1. Only triggers on an item or file updates, not on an item or file creation.
  2. 'Get item or file properties changes' action
    1. This new action returns information about whether or not a column's value was modified.
    2. This action when released will:
      1. Only work with the 'When an item or file is modified' trigger.
      2. Require versioning to be turned on for the associated list or library 


With these two updates, you can now build a flow when someone modifies a list or library and then using the new action check if a particular column or file property was modified since the last flow run. For example, you can check if the Status column was modified since the last run and then get the current Status value, else do something else.  


After this update, we will continue to work on enabling the 'Get item or file properties changes' to provide old and new values of the columns as well. 


Thank you all for being patient with us. Will update this thread as we have more updates.




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!!

New Member

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.

Advocate I

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...