@tpagett-finxact Flows within a flow is a definite possibility not just to reduce visual complexity but for modularity as well 
2 Likes
Thanks a lot @samayverma!
Can you please help with one other issue I see:
When I trigger workflow, I see more than one call for each “Send Request” step.
Am I missing something here? Not sure why it’s getting called multiple times.
This looks like a bug. We’ll look into it and fix it 
I currently have multiple folders with steps for my flow:
Folder 1 has 3 Restcalls and a prerequisite step (on the folder) which is super important to setup the data
Folder 2 has 2 Restcalls with a prerequisite which is also important.
I am missing an option to select complete folders to be executed.
So in my flow i would just do Folder 1 ----> Folder 2
Right now you can execute a folder as a singular unit, But all of its requests together.
Your pre-request scripts will still work if you have those request on the flow. If you have workflow logic in the scripts, a easier way would be to make it in the flow itself 
I am not seeing an option to select a complete folder in “Send a Request”, am i missing something?
Also in my tests it seems like that prerequest scripts are NOT executed.
I added a simple console.log, but iam not seeing it in any console. Also iam adding consecutively variables to the environment in a flow (via prerequest script and test scripts) . This is somehow not working as the sendrequest shows empty variables.
Is this working and the error is on my side?
Thanks for the answer
Hey,
Awesome new features. I have two questions after some playing around.
-
How do you handle variables along with the flow? I would expect that I can set global variables like tokens for manipulating multiple users. Seems like, if I have a global variable, then the flow cannot overwrite the value stored there.
-
How can you join more than 2 threads of execution. There is the “Combine” but that only works properly for 2 threads. Would be nice to not create log2(n) combine elements in a chain to join n threads.
Even I see pre-request scripts are NOT executed when the request is run in a Flow…
Thank you for acknowledgement
Hi can I know how to accomplish something like this?
What I want is idToken & id variables both available for the last request, but only one is available.
Is this a bug? I tried using combine but that’s not working either.
Is there any documentation for Flows?
1 Like
Docs are in progress, and should be out shortly. In the meantime, here’s part of the livestream where we walk through it slowly: Flows to control your workflow graphically
1 Like
Hi @germanynick, we have the plans for API to trigger flows on our roadmap! So eventually you will be able to trigger flows using some form of webhook or API call.
Hi @Isuruimesh,
This flow should’ve worked as you expected. Not sure only one variable is available for the last request. Would you please let us know which of the two variables is not available?
Hey @askmeagain,
With flows, we are trying to get away from the implicit flow control provided by folders. In the near future, you will add support for running one flow inside another flow and also provide an easy way to import/migrate folders to flows.
So what will this look like in the future then
Flow 1 - This will be your prerequisite step
Flow 2 - This your other two calls
Flow 3 - This will be where you combine Flow 1 → Flow 2
The few benefits that we think you would get with this approach is that you can reuse the same flow/steps in multiple different scenarios without needing to duplicate requests. Use folders more effectively to organise your request for better documentation without worrying much about execution order.
Let us know what you think of this!
1 Like
Hey @kemenesbalazs!
Thank you for trying out the feature and welcome to the community
-
Flows will honor all Postman variables. If you create a variable within the flow (via the create variable block), those are the local variable which will override all the other scopes. You can read about the scopes here: https://learning.postman.com/docs/sending-requests/variables/#variable-scopes
-
I didn’t quite get what you mean by joining “threads of execution”. Would you please explain your use-case here (possibly with an example)? In general, you can branch in or out just by using the connectors. You can refer to the next immediate screenshot posted in the thread.
Hey @kemenesbalazs ,
How do you handle variables along with the flow? I would expect that I can set global variables like tokens for manipulating multiple users. Seems like, if I have a global variable, then the flow cannot overwrite the value stored there.
Could you explain what you are trying to achieve here in a little bit more detail? Passing data into the request blocks with the same name as the global should ideally override that.
How can you join more than 2 threads of execution. There is the “Combine” but that only works properly for 2 threads. Would be nice to not create log2(n) combine elements in a chain to join n threads.
Synchronization in flows is achieved by using the signal ports, these are the ones at the bottom of each block represented by a green box with ON written beside it. And the corresponding grey box.
If you just want to synchronize a block, such that it is executed only after a few other blocks have been executed then connected their output signals to the input signal of the block that you want to defer. Data can also be used as a signal, in this case, you connect a normal output port to the signal input port.
Alternatively, if you want to merge two data packets into a single packet you should use the COMBINE block, which, as a side effect also does the synchronization not but not really intended for that purpose.
Also if you can let me know the use-case I might be able to suggest a good way to achieve it.
Hey @askmeagain!
Currently, we support executing only a single request in the “Send Request” block not folders or collections.
We do support execution of prerequest scripts. But currently console.log would not work in flows. We are looking into fixing this as soon as possible.
Thanks!
Yeah sure I’ll explain it & thanks for the response,
This is the request body, and you can see id is not filled with the variable.
But in the headers, authorization header is filled with token variable.
