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.
We are now working on this and will release it in the next couple of months.
It will help us to split the indpendent flows and converge them into one based on the business need.
Use HTTP Post/Request, similar to what's described here: https://flow.microsoft.com/en-us/blog/build-nested-flows/
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.
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.