← Back to Luvin
Luvinvs
Postman Flows
Postman Flows gives you a canvas to build a chain. Luvin reads your contracts, builds the chain and tells you if it works.
| — | ||
|---|---|---|
| Starts from | Requests you already built, one by one, in a collection | Your OpenAPI and AsyncAPI contracts: every operation is ready to drop in |
| Wiring the data | You connect each block’s output to the next block’s input by hand | Wired for you by rules: tokens, ids and fields find their source, and missing values become inputs |
| Test cases | You add each check yourself, block by block | Generated from the contract: happy path, invalid inputs, no credentials and every documented error |
| Coverage | What you remember to check | Every documented response is listed, so you see what the journey does not handle yet |
| When a contract changes | You find out when the flow breaks | Luvin tells you which journeys the change breaks, before you run them |
| Without a live API | Needs the API, or a mock you set up first | Simulates every step from the contract examples, with zero setup |
| When something fails | The block that errored and its raw response | A verdict in plain words, with the step and the field highlighted |
| What you keep | A flow that lives in Postman’s cloud, behind an account | An Arazzo file on your machine: open standard, in git, runs in CI with any Arazzo runner |
Use Flows to automate and deploy workflows. Use Luvin to prove a chain of APIs works, and to see exactly how the data moves through it.
Based on each product’s public documentation as of November 2026. Postman, Postman Flows, Bruno and Insomnia are trademarks of their respective owners; Luvin is not affiliated with them.