DEV Community

Cover image for I got tired of writing Postman scripts to pass tokens, so I built a visual API chainer
Shubham
Shubham

Posted on

I got tired of writing Postman scripts to pass tokens, so I built a visual API chainer

Hey devs! 👋

Let's be honest. We’ve all been there: You want to test a simple API sequence.

  1. Hit the /login endpoint.
  2. Extract the JWT token from the response.
  3. Pass that token into the Authorization header of the /get-profile endpoint.

In traditional API clients, doing this requires switching to a "Tests" or "Scripts" tab, writing something like pm.environment.set("token", response.json().token), managing environment variables, and hoping you didn't make a typo.

There are visual tools out there (like Postman Flows), but they often feel like heavy cloud-automation monsters built for enterprise orchestration, not simple local debugging. Plus, they lock you into recurring team subscriptions.

I just wanted a lightweight, local, and visual way to see my data flow from API to API. So, I built one.

Enter Aaptics_Flow 🚀

I've spent the last few weeks building a purely visual API canvas that runs entirely in your browser. You can check it out here: flow.aaptics.in

Instead of writing scripts, you drop API nodes onto a canvas and draw wires to connect the output of one API directly into the Headers, Query Params, or Body of the next.

✨ Why build another API tool?

I wanted to focus on three main things that frustrated me with existing tools:

1. 100% Local & Private Execution 🔒
Most visual API tools run your requests through their cloud servers. If you are dealing with sensitive production databases or internal auth tokens, that's a security nightmare. My tool executes requests directly from your client/browser. Zero server-side logging. Your data stays yours.

2. Visual Debugging, No Scripts 🔗
If an API fails, you can visually see exactly where the chain broke. You can inspect the exact payload that was passed through the wire from Node A to Node B. No console.log() needed.

3. Goodbye CORS Issues
To make browser-based execution work smoothly without CORS blocking every request, I built a lightweight proxy using Cloudflare Workers. It acts as a seamless bridge so you can test any public or private API without tearing your hair out over preflight errors.

🛠️ The Tech Stack

For those curious about how it's built:

  • Frontend: React (Handling the drag-and-drop node canvas rendering smoothly).
  • Backend/Proxy: Cloudflare Workers (Extremely fast edge proxy to handle CORS and license validation).
  • Payments/Auth: Dodo Payments (Merchant of Record to handle global checkouts seamlessly).

I need your feedback! 🙏

I just deployed the free version and I would love for the Dev.to community to tear it apart.

  • Is the drag-and-drop UX intuitive?
  • What node types or features are missing for your daily workflow?
  • Did you hit any bugs?

Try it out for free: https://flow.aaptics.in

Let me know what you think in the comments! Happy chaining. ✌️

Top comments (0)