Showing results for 
Search instead for 
Did you mean: 

SharePoint trigger When an existing item/file is modified

You need to re-add the "When an existing item is modified" and "When an existing file is modified". It was replaced by "Created or Modified" and that is not sufficient. There are cases where certain logic is only executed on creation, and other logic only on modification. Now, don't get me wrong, created and/or modified running the same logic also has uses!


With only having the trigger "created or modified" and wanting only certain logic to run on a modification, I have to add logic to ignore creations. You're making more work for your users and taking away basic functionality.

Status: Under Review

Hi everyone, thank you for the feedback, and apologies about the frustration you are feeling.


To clarify, we never had a "When an item/file is modified" trigger. It was called that, but the behavior was the same as what we have today. So we merely renamed it to reflect what it was doing, as it was causing a different kind of frustration.


The best way to identify item modified remains checking for the difference between created and modified timestamps to be "close enough". Most of the time these will be the same. However, things get out of sync when a large file is being uploaded, where the library item will get created, and then the file upload will complete and change the timestamp. Similarly, when creating a list item, first the item will be created, and then you will have modified events when each attachment completes uploading.


We will review how we can make this experience better, but it is a little challenging due to the reasons I tried to explain, so it will not be a quick fix that will be coming in a few weeks.

Not applicable
Helper I



Status was changed to 'Under Review'.  Is there new updates on this?

I have a requirement to use this if it is available.



Advocate II

Is there any update on this? Agree with all the above, this is required !!!

Advocate III

@LauraEmbersonI don't think they care. For a product that isn't included with SharePoint and to which they are subtly directing people to use to replace SharePoint Workflows, the support isn't good. The thing that still gets my goat is that this is obviously possible. SharePoint workflows have a "item modified" event that they can latch onto, so there is definitely something there that allows it. Why they can't hook Flow into it? I have no idea. I don't know what language Flow is written into but I'm pretty sure the SharePoint API has events you can subscribe to for stuff like this. Not very encouraging. I don't recommend Flow to other people, mostly because of stuff like this.

Not applicable

Is there any expression that we can use to usbstitute this and while Microsoft will add it back.


Advocate III

They haven't posted anything about this in forever.


I guess what workaround (sigh) you could try is to use their new feature where you can limit what is returned by the connector to a certain view. You could make a view that only has items modified that day or something, I dunno.