I gave REST workflows one workspace developers actually stay in.
How it was built, and why
Restflow replaces brittle scripts and disconnected collections with one workspace for the full loop: import or define an API, build a workflow visually, test it, then monitor it in production.
The flow
The core loop is import or define your APIs, build the workflow visually, test and validate instantly, then monitor and iterate continuously.
What it is
A complete product surface, not a landing page: onboarding, a drag-to-build workflow builder, run history with per-run detail, a monitoring dashboard, an integrations and marketplace layer, plus account and pricing.
Visual builder for chaining REST calls with no glue code
Live run history with drill-in detail per run
Monitoring dashboard for ongoing health
How it works
I built the builder as the spine and let everything else hang off a run: a run has a timeline, a detail view and a monitoring signal, so the same object carries a developer from authoring to production.
Integrations and a marketplace sit alongside onboarding and settings so the workspace feels like a place to stay, not a demo to leave.
Why it matters
Developers were stitching Postman collections to cron jobs to dashboards. One canvas that covers build, test and monitor removes the seams where things silently break.
