01 · AI Workflow Automation
Flowys.
Automation for the jobs that start with reading something: a support email, a meeting transcript, a pile of reviews. You lay the job out as steps, any step can hand its work to an AI, and nobody is ever asked to write JSON.
◉ 3 days
AI Workflow Automation
Role
Product Design · Full-Stack Build
Team
2 Developers · built with Claude Code
Year
2026
Timeline
3 days
Stack
Next.js · TypeScript · React Flow · MongoDB · OpenAI · Tailwind CSS
ch.01 · ChallengeChallenge.
The app worked, but running a workflow opened a modal asking for JSON. That put the one thing non-technical people cannot do between them and everything the product was for. Removing it meant covering every config shape in the app, not the three that were easy.
ch.02 · ApproachApproach.
Rather than enumerate the known shapes and hope, the editor mirrors JSON's grammar itself: object, array, text, number, yes/no. That makes it correct by construction for shapes nobody has thought of yet. Everything downstream followed. Plain-language run forms, templates that are whole jobs rather than demos, and results a person can read.
ch.03 · OutcomeOutcome.
Typechecks and unit tests passed clean while three real defects were live: a model retired six weeks earlier, list schemas rejected before the model was called, and string comparisons that were always false. A suite that talks to the real OpenAI API and real endpoints found all three in one run. Every template now runs end to end, and the app reads the same as its marketing site.
In the build
What I owned.
- 01Removed JSON from the interface with an editor that mirrors JSON's own grammar, correct by construction for shapes nobody has thought of yet
- 02Run forms in plain language: paste the email, upload the transcript, answer the question
- 03Six ready-made workflows of ten to fifteen steps each, every one running with no accounts to connect
- 04Flux, an assistant that turns a sentence into a working ten-step workflow and diagnoses a failed run
- 05Results rendered as formatted text rather than a JSON dump
- 06A live test suite against real models and real APIs, which is what actually caught the bugs
// outcome
10-15
Steps per template
None
JSON to write
None
Accounts to connect