Launching today
Luzo
Design and debug API workflows visually
91 followers
Design and debug API workflows visually
91 followers
Luzo is a desktop-first, open-source tool for building, running, and debugging multi-step API workflows. Instead of treating requests as isolated calls, it lets you design dependency-aware flows, pass variables between steps, inspect execution through a live timeline, and retry from failure without restarting everything. Built for developers and QA teams working with real API workflows, not just single requests.
Luzo
@janasundar Quick question: for someone chaining APIs daily, how does the visual flow builder handle conditional logic, like "if response X fails, retry or branch to Y"? Feels like a game-changer if it's intuitive. Congrats!
Luzo
@swati_paliwal Hi! That’s a great question.
Right now, Luzo focuses on making API flows easy to understand and debug:
If something fails, you can retry from that exact step without running everything again
It automatically figures out which steps depend on each other and runs them in the right order
It doesn’t support automatic “if this fails, go here” branching yet
For now it’s more about clear, step-by-step execution with strong debugging.
That kind of conditional flow is definitely something I’m looking to add next 👍
How does the live execution timeline work when you have parallel branches in a flow, does it show all steps running simultaneously or queue them visually? Congrats on the launch!
Luzo
@borrellr_ Thanks! Parallel branches show as concurrent when they’re eligible to run at the same stage, while dependent requests appear sequentially based on their execution order. Each step still keeps its own state and details for inspection.
Luzo making API workflows visual instead of cURL-heavy is the right call. The real test will be auth flows and rate-limited responses, since those never behave the same in staging as they do in production.
Luzo
@piroune_balachandran Totally agree. Luzo already helps inspect multi-step auth flows and failures step by step, but the honest answer is that deeper handling for things like token refresh, branching on auth errors, and smarter retry/backoff for rate limits is exactly what we’re building toward next.
Super interesting! How does Luzo handle branching logic or conditional flows? Can you create complex decision based workflows easily?
Mokkit
Hi fellow hunter! I'm also launching today (Mokkit), just checked out your product
Such a cool idea, it changes from all the AI and agent launches, I wish you success and upvoted you!
Luzo
@ugo_builds Hi fellow hunter! 👋
That means a lot, thank you! Just checked out Mokkit as well, looks really interesting 👀
Really appreciate the support and the upvote. Wishing you a great launch too 🚀
This is a really solid idea👏Most API tools down once workflows get complex so having a dependence aware system with a live timeline is a big upgrade .Love the developer first approach.