cancel
Showing results for 
Search instead for 
Did you mean: 

Multiple Triggers For The Same Flow

Saw this posed as a question so figured I would throw it in the ideas. It would be very useful to have multiple triggers set off the same flow, especially if they are similar triggers. For example, right now if I have a BI alert for two different tiles that are both cards that must email the same people, I need to create two flows. It would greatly reduce the amount of Flows that need to be managed if either of the alerts could set off the same flow. Also, if they are similar enough as the same BI cards it would be nice if they could perform a merged action instead of two seperate ones. Example being if two alerts are set off in BI for tiles, and those tiles need to be emailed to the same people, Flow would send one email to the list containing info about both of the alerts. Thanks!

Status: Declined

This can be accomplished by using multiple flows pointing at the same business logic via a child flows:

Flow 1 with Trigger 1 and Child flow action

Flow 2 with Trigger 2 and Child flow action

Flow 3 with Trigger 3 and Child flow action

Flow 4 with Button trigger and your actions

 

We do not have any plans to have many triggers in a single flow.

Comments
karenmoret
New Member

I'd like to trigger my flow for a selected item in a sharepoint list and when a new task is created, to update the new task based on the list item inforamtion. Having more than one trigger would make my life easier to have it accomplished. If anyone has an idea to wrokaround it I'd very much appreciate it.

JR-BejeweledOne
Super User

Please add this.   We should have the option to automatically trigger a flow such as when a new item is created or trigger it manually for SharePoint.

 

All other workflow products have this option for SharePoint

tonygarcia22
Frequent Visitor

This would be great, feels like the power of the Automated Flow tool is very limited because of this. My flow is limited to just 2 steps because of thisFlow error.PNG

swingline22
New Member

It's been quite some time that this was requested, but no traction. Multiple triggers are needed and would make use of different types of conditions , such as two different SharePoint lists, but the actions, and the groups are the same. Additionally the pricing model of power automate does not scale well if you want a consistent workflow to occur. If a individual user leaves how easy is it to transition their flows prior to deactivating their account?  As 5 flows cost $500 /month to be separated from an individual user ...The solution here asks you to create 4 separate flows to complete 1 single process effectively wasting your allotted flows. https://flow.microsoft.com/en-us/pricing/

 

To me this is a great starter for good ideas on making some simple workflows, but this doesn't scale well at all.

 

 

Billy_C
Helper V

I really think that this could be usefull in many cases, for me it would be really logical if it was possible to implement triggers parallel from each other like you would with actions. This way if information from different sources are being created/updated or removed all are being updated correspondingly or emails can be send no matter which trigger is used.

 

The best way on how to see this is by thinking that the triggers are inside a switch and you use variables as the central data source to place the data of that trigger on to the variable so that no matter what trigger is executed all data is coming from that variable.

 

Or perhaps something like a trigger store could be used that keeps all the triggers together and if you want to use the data from the trigger you retrieve it from the store perhaps with a status so you know which trigger was executed so that you can use conditions to execute different steps based on that status.

Stephen
Power Automate
Status changed to: Declined

This can be accomplished by using multiple flows pointing at the same business logic via a child flows:

Flow 1 with Trigger 1 and Child flow action

Flow 2 with Trigger 2 and Child flow action

Flow 3 with Trigger 3 and Child flow action

Flow 4 with Button trigger and your actions

 

We do not have any plans to have many triggers in a single flow.

Billy_C
Helper V

@Stephen,

 

I agree that you can do it that way, but power automate has a limit to the amount of flows that can be created.

Applying your principle increases the amount of flows that are created as in my case I have 6-7 conditions on when to create an invoice based on project updates, crediting a different invoice or receiving deliveries. Meaning that I would need 7-8 flows to be able to support this. Knowing that there are many other scenarios where multiple conditions spread over multiple entities, this makes it hard to stay within the limit.

Although the limit is high, it's easy to get there once you're expanding your current CRM system to support different processes.

 

As in my case I already have around 20 flows in order to create invoices, orders, deliveries, payments, staffels,  staffel history, application history. And I still have to build reminders, inventory history and many other features. I made as easy as possible, like combining multiple flows into one, but where I check whether the trigger is executed for update or creation. For example sending out reminders will take up around 7 flows, then I also have inventory history to track, task tracking etc. When taking a look around to see how many more flows I will have to create, then I get around 30 maybe even 50 depending on these triggering conditions and how well I am able to combine them.

 

Being able to group conditions might make it possible to minimize the amount of flows, depending on how many flows can be grouped together. As in my case, it might be 2-5x times fewer flows that have to be created to get the same result. Which makes it easier to manage and update when issues arise. For now, it's okay as I haven't reached that limit and can still manage it, but in a year or so this won't be the case. So I think future wise that this is something that should definitely be taken into consideration.

 

Or, that is at least my opinion on the possibilities of this topic.

clechner
Advocate I

This one isn't likely to happen. Sorry all.  Architecturally it adds too much overhead. 

@Billy_C  - 7 flows for reminders sounds like a TON.  I have a reminder system in Sharepoint that uses a single list with a single flow, which handles recurring reminders as wel.  Yours is probably faaaar more complicated, however.  When I did it I remember thinking, "I should be able to create a reminder in here from anywhere.... doesn't matter."  

 

supermankelly
Regular Visitor

Overhead? You can create "hidden" flows so it's no different than a user creating multiple except users do not have to create and manage multiple. Just the one flow in the UI but in the backend it's multiple. 

 

Flow in UI from users perspective:

T1 -->

T2 -->      A1 --> A2

T3 -->

 

In backend its 3 flows: (No change)

T1 -->      A1 --> A2

T2 -->      A1 --> A2

T3 -->      A1 --> A2