Power Automate

Sharepoint trigger when item is created or modified or deleted

(0) Share

Report

Posted on by arkkgroup

154

I want to create trigger when list item is created, modified or deleted.

I can see 2 different triggers: one for create or modified, another for when item is deleted.

I don't want to have 2 triggers. Is any way I can combined them?

Thanks

Categories:

General topics

I have the same question (0)

All responses (4)

Answers (0)

Sort by

v-bofeng-msft Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @arkkgroup ,

No, I'm afraid there is no such a trigger.

Best Regards,

Bof

Was this reply helpful? Yes No
angelan92 10 on at

Like (0)

Report
Copy link

Link copied!

I was hoping that there was a solution for this. Hopefully when a new update comes, it'll have this option.

Was this reply helpful? Yes No
Suggested answer

CigarDoug 9 on at

Like (0)

Report
Copy link

Link copied!

There is an easy solution to this: Three flows.

Flow 1: Triggers when an item is created or modified, first action is to call Flow 3.

Flow 2: Triggers when an item is deleted, first action is to call Flow 3.

Flow 3: Manually triggered, contains all the other actions.

CigarDoug

Was this reply helpful? Yes No
David_MA 14,509 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Can you share why you want a single workflow to handle create, modify, and delete events? You would normally split these events into two workflows:

Workflow 1: Handles create and update events

Workflow 2: Handles delete events

The main limitation is the delete trigger. When an item or file is deleted, Power Automate only receives very minimal information (typically just the ID). At that point, the item no longer exists in SharePoint, so you can’t retrieve column values, metadata, version history, or related content.

Because of that limitation, a single trigger that fully supports all three actions isn’t very practical. It is unlikely Microsoft will introduce one. The data available for create/update events and delete events are different. Once something is deleted, your options are limited, which is why splitting the logic into separate workflows is the most reliable and maintainable approach.

About the only time I use the When an item is deleted action is when someone wants to be notified that a file has been deleted. I am sure people have found other uses cases for the action and would be interested to hear about them.

Was this reply helpful? Yes No