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.



New Member

It just seems to simple a request- especially if you want these products adopted by a wider market, you need to make it point and click as much as possible. I have my hands full as it is and don't have time to dedicate to learning JSON or other overly complicated flows. 


Scenario- i have an off boarding SPO list. When a specific field is modified, or a group of fields, i want to trigger emails to specific users in the org, ie 'remove mailbox and network access' field is updated trigger an email to user x.


At the moment this seems to be impossible. 

Power Automate

Hi all,


As posted earlier, we are looking into how we build this capability into SharePoint triggers. There is no need to post another item in the SharePoint User Voice as the product team is already monitoring the request here. 




New Member

Hi Chaks,


thanks for the reply- yes i know you are monitoring this but by the date 2/8/18 is sometime ago now, and as you mentioned the eta was early this year. When can we have an updated timeframe for this request? It's absolutely critical otherwise we're unable to leverage these systems to their full potential. 

Not applicable

@Chakkaradeep ; any deadline for this change, as it is weird to receive same comments from Microsoft for last 2 years..

Advocate II

Come on please. We really need this feature. 

Helper II

must to have option in Flow

Advocate III

is there any status updates? 

Frequent Visitor

It would be good even if we could get a modification to the trigger condition to allow for instance a "@onChange(" expression, as that would solve the requirement for granularity.

Resolver I

Looking for an update to this as well. This could be a potential dealbreaker using Flow/Power Automate with the workarounds running EVERY TIME instead of only firing on this event.

Power Automate
Status changed to: Planned

Hi all,


Happy to say we are planing to start this work in April.


The first deliverable will be a new action that will get changes for one or more columns in a list or library using versions. The action will not only return the columns changed but also all values for each column since the last time the flow ran, thus bringing support for new and old values. You will be able to use this action in your existing flows with the 'when items are created or modified' trigger and still get to know what columns changed and their values. 


The second deliverable will be a new trigger 'When a column value changes in a list or library'. This requires more development time. However, we believe the new action will be sufficient for all scenarios and also helps to close this idea as well


Can't wait for this to land! Let us know what you think!