Postman Flows V2: What’s New

I’ve been wrapping my head around the latest Postman Flows early access release, and this one is a biggie. Of course it is still subject to further change still, but as outlined by the team in the linked post, the major changes to the current beta version of the low code API workflow feature called Flows are:-

  • Massively simplified list of blocks, probably around 50% are left (those that didn’t make the cut include Test Summary, Create Durables and Conditions blocks to name a few)
Youtube video showing the simplified block list in Postman Flows
  • Back by popular demand, the return of the Start button – don’t call it a comeback!
  • End of Terminalslog blocks can now be added instead, which pumps data to the console log
YouTube video showing console log entries appearing for tests following execution of a Flow
  • Webhook blocks – can now be added in order to trigger Flows from the Cloud – this will make CI implementation of a Flow possible as the Webhook URL that is generated when a Flow is created can be saved and called called like any other Postman request, as well as allowing a Flow to be triggered automatically by an event, say, a Slack or Discord message
  • The arrival of Flows Query Language (FQL). FQL aims to low code-ify data that is used in our API requests and responses, to allow that data to be easily queried, accessed, reused and changed in a much simpler way than by writing complex JavaScript pre-post scripts against the APIs themselves.

I suspect FQL will be subject to tweaks, but everyone acknowledges that the click and hope method used prior to this was pretty painful. To my mind it looks a lot more technical (and therefore a bit more scary for a new user to pick up) this way, so I’m hopeful that with plenty of feedback the team can continue to make the experience simpler. However FQL allows us to:-

  • Generate standalone data (e.g. current date/timestamp) to use
  • Pull data from a Flow (e.g. a response body value) to use
  • Create our own variables (e.g. no times to iterate a test) to use

From what I can gather, any of these can get fed as an input into an evaluate block which can query that data, then output the result. So for example, GET all bookings, then evaluate which booking ID’s are greater than 7, then output those booking ID’s which meet that criteria into the Flow to do what you want with e.g. add an if statement. I can’t quite get this to work at the moment though, so I’ll intend to update this blog once its a bit clearer in my mind!

Youtube video shows an early attempt to work out evaluate block using FQL


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: