Postman Flow Builder: Usability Beyond Testing?

Hello Forum,

I hope you can help me with a question I have about Postman.

I’m exploring the possibility of using Postman’s flow builder for our API projects and am having some trouble finding information about its use in a production environment. While I’m not a super user of Postman, I’ve occasionally used it for testing API calls. Recently, I discovered the flow builder feature and am trying to determine if it can be used for purposes beyond just testing.

Specifically, I’d like to know if a flow built in Postman can be deployed in such a way that the results are accessible or downloadable. I’m unsure if Postman is designed primarily for single API testing or if it can be utilized for more comprehensive, production-level tasks.

Could someone provide a short answer on this and point me to the relevant documentation? I find the Postman flows to be a powerful tool, but we need a solution that can build and deploy flows to run in our production environment as well.

Thank you in advance for your help!

Hi @btc27

Welcome to the forums!

This is a great question. Flows can and is being used in production environments by many of our customers today for a variety of different use cases involving integration/automation. We also use Flows internally to power a lot of our applications and automations :slight_smile: .

We have a comprehensive learning center that can walk you through each step of building with Flows. The use-cases you’re describing would fall under our advanced tutorials if you want to have a look.

Regarding accessible results, you can send the output/logs/final payload (whichever piece you need) to a third party system via an API request within the Flow (Airtable, Slack, etc.).

If you run into any issues or would like to have a more in-depth discussion, i’d be happy to jump on a call to hear about your use-case and concerns.