I have a Flow "A" and i want to build a Flow "B"
Flow A should start Flow B
- Flow Management
- Turn on Flow
- Start Flow B
Now, i want to build Flow B
First of all i need a trigger?
But this is exactly my problem. Which one is right?
I dont want Sharepoint or Outlook or PowerApps as trigger.
I want another Flow as trigger but i dont find this Option!?
What can i do?
I hope you can help me.
You can trigger Flow B directly from Flow A using an HTTP request action. This will require premium licensing but it works. Take a look at this article
first of all thank you very much for the fast response.
I just read the workaround from the o365tech8 website and yeah what should i say.... it looks complex.
I dont unterstand why it should be so complex.....
To start a flow as trigger from another flow is an obvious scenario for me...
I am a little disappointed but i will try the solution.
I will get in touch later.
An out of the box workaround (albeit, with some limitations) could work if the context is SharePoint.
Have Flow A set a yes/no column on a SharePoint list item, which acts as the Flag for Flow B.
Have Flow B run on a schedule to Get Items from that list where those items have been flagged (use a filter) and then execute.
At the end of Flow B, update the SP list item to NO to unflag the item.
If this response provided an answer to your question please mark it as a solution.
If you liked my reply, please give it a thumbs up! Thank you!
thank you for the answer.
This is a good point... i already think about it.
I work with powerapps and i try to build a business solution...
The workflow is complex and i have roughly 20 flows....
If i do this with sharepoint list items it could be very fast very confusing...
especially to monitoring later.
I will think about the Solution with Sharepoint and HTTP Reguest again and i will decide.
I hope microsoft will build this function in the future.
I understand what you're trying to accomplish, but I'm curious as to why you would want to do this. If Flow A always triggers Flow B, why do you want two separate flows? Why not just make them a single flow?
Regardless, a simple solution would be to end Flow A by creating something any place where you can store a value or object: a queue, a file, a SQL table, etc. The trigger for Flow B would be to watch for that object/value to be created. Then Flow B would end by removing that created trigger value. For example, Flow A ends by creating an empty text file in a OneDrive folder. The trigger for Flow B is watching for a file to be created in the OneDrive folder. Then, when Flow B ends, it deletes that created file.
Thank you for the answer barret,
but I'm curious as to why you would want to do this. If Flow A always triggers Flow B, why do you want two separate flows? Why not just make them a single flow?
This is exactly what i dont want to do. As i say i have around 20 Flows and Flow A dont triggers always flow B.
a simple solution would be to end Flow A by creating something any place where you can store a value or object: a queue, a file, a SQL table, etc. The trigger for Flow B would be to watch for that object/value to be created.
Yes, i think this will be my way to solve the problem.
Ich will try this 🙂
Three Super User rank tiers have been launched!
Features releasing from October 2020 through March 2021
We are excited to announce the launch of Power Virtual Agents Community. Check it out now!
We've updated and improved the layout and uploading format of the Power Automate Cookbook!
Fill out a quick form to claim your user group badge now!