Showing results for 
Search instead for 
Did you mean: 

Trigger flow When Item is Modified only


There is no trigger in flow when Sharepoint item is modified with specific field(s), instead of this we use when item is created or Modified with add condition after triggering the flow. Major draw back for using above mention trigger is to always trigger our flow when item is modified which may results out flow runs as they are limited. Please look into this issue ASAP. we need it badly.




Status: Completed

Thank you @Chakkaradeep for sharing 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.

Kudo Kingpin

@teqs Yes I go through it and i already give approval to admin to merge my thread with already existing Thread So our Votes will merge to that thread.





New Member

The trigger works; it works when any action is done that qualifies as a modification: file creation, edit, save. One file gets added to a Sharepoint list = 3 alerts/emails. 

One item already in the list gets opened (1st email), edited or save whilst it's open (2nd email), and saved (3rd email). 


What I'm asking for, what I'm trying to do a better job of asking for, is a Flow where the Team gets notified if a file's contents change. 

i.e. Larry, Curly, and Moe would get a notification if and only if Shemp opened a file, made an edit, and closed/saved the file. 


Here's hoping this furthers the conversation, 


Advocate I

It would help a lot to have this implemented. The way it works today with the "When an item is created or modified" it always fires the flow when the item is created and you definetly do not need that. 

Even better would be to have a trigger : When an item is modified" which would fire only when when specific fields are changed. 

Kudo Collector

There are similar suggestions. Please upvote these also.


Trigger on specific column and this idea includes "only trigger on edit":


Also to prevent self triggering:


Also to get previous values on modification. I think most people who need trigger on modification want to know previous values.


I hope MS include all of these together. Because all of them is a very, very similar topic. This should include provide trigger which only fires on edit, which this idea is about.

Not applicable

Here's a use case for why this "trigger on modified" is so important:


In a SharePoint Library, user clicks "New Document".  The content type for this document includes, among other things, a People field called Reviewer.  This allows the submitter to enter an appropriate name of the person who will receive the Approval request.


When the document opens, Word Online saves it immediately as "Document.docx", after which the user can change the title.  But there are no options to add values for other column metadata in the library, which means the "trigger on created" has already occurred by the time the user can enter a Reviewer name or other important columns.


This is what happens when a new development team with apparently little knowledge of existing options creates a "modern" version.  "Modern" sites are full of gaping holes like this.

Helper III

I just got out of the meeting with the MS Premier Support. They were able to duplicate the infinite loop but could not come up with a workaround. They could not explain either the reason for the Flow Production team nuking the modified trigger only to merge create or modified into one trigger. I told them that this bug has been going on for years now and it seems MS just ignored - they just apologized!


Anyway, the Premier Support team is in contact with the Flow Production team but no estimated time for a resolution.


I will inform this thread for any updates.

Regular Visitor

A must to have option in Flow.. badly needed for several flows that i am developing on..

Please make this as a priority item.

Advocate IV

With the new trigger options a workaround can be implemented to check if the created date is equal modified date. If it's qual it's a new item if the modified date is different it has been modified.


Did not try it myself so far, thoug....

Kudo Collector


Nevermind. I got excited, but this trigger fires on a newly created item. It's NOT only on Modified, even though that is how it's titled. ☹️


My colleague found this template, which seems to have exactly this feature:

You can start from this template and then delete the actions you don't need. I'm trying it now b/c I have a use case where hundreds of list items get created at once and I DO NOT want the flow to kick off. But it DOES and then it throttles the site. The flows never get past the trigger action. Trigger completes successfully but then it hangs forever even though the next steps are incredibly simple.

Kudo Collector



My initial tests comparing Created and Modified dates seemed successful, but since then, the Flow has started finding the condition False and continuing on its merry way. I guess it's just inconsistent. Sometimes Created and Modified match exactly and sometimes they don't. It's just a pain. You can do this in SP Designer, for cryin' out loud.


Things would be so much easier if it were possible to trigger on Modified ONLY. Trying the workaround of checking to see if Created date = Modified date. If Yes, then terminate Flow.