Showing results for 
Search instead for 
Did you mean: 

Flows trigger other flows

This feature would be fantastic for creating a modular environment. The passing of parameters between flows and essentially creating the ability to make functions would make flows an irreplacable asset to my work.

Status: Completed

This item was part of the October 2019 release :

Kudo Kingpin

Want the ability to Nest an Existing Flow within a Flow - Like in Logic Apps -

  • So we can get around the limitation of a single action within a Do Until
  • Make Flows more moduar and reusable
  • Open up the opportunity to build common or complex Flows as templates that can be embedded within end-user Flows
Not applicable

It will help us to split the indpendent flows and converge them into one based on the business need.

Frequent Visitor

This is possible using the HTTP action and wrapping a manual request/response Flow in a custom connector so that your users can select your actions from the action list like any other action. My concern is that I quickly hit the 50 Flow limitation which does not make Flow a great platform to roll out enterprise workflows for large organisations.

Not applicable

Use HTTP Post/Request, similar to what's described here:

Advocate IV

Cascading of Flow into another flow will help to utilize reusability of the code.

A large piece of flow can be re utilized making this system as component based.

Helping easyness.

Not applicable

it would be great to have an action that would trigger another flow.  


This would allow for organizing individual tasks into smaller, easier to understand flows.  One task per flow, but linking multiple flows via an action that can start the next flow in the chain.


Currently, there is an action called Start Flow which many people on the forums confuse as being able to trigger a flow to start.  Based on the number of people trying to use this action, there is clearly a need for this function.

Advocate I
This is accomplished by creating a Flow with a Request trigger and then using the HTTP action to call another Flow based on the URL of the Flow with the Request trigger. You can even pass through parameters to another Flow through the trigger schema in the body of the HTTP action. To make it an even nicer experience you can wrap your Flow to call in a custom Connector so that you can then see all your other Flows as Actions and supply friendly parameters (text boxes, drop-downs etc.) instead of writing json to pass through your parameters.
Not applicable

Based on the number of votes on this, I would consider the solution recommended to not be sufficient.  It may work, but I have tried it and been unsuccesful.  


I would also add that if the HTTP action is the recommended way of doing this, it needs to be renamed.  

Advocate III

In addition, the HTTP action pattern is not a user-friendly pattern. It is best suited to small modular actions like sending an email since it involves passing data in JSON objects that have to be built manually. This does not fulfill the no-code nature of the Business Application Platofrm. We need a method to nest a flow within a flow so that can be done easily within the UI without manually building JSON objects.

Frequent Visitor

I would like to see this.  It would enhance our ability to reuse flows.