Why has a workflow editor from 2019 thrived for seven years?
- Contribution
- Lead designer, recipe editor
- Team
- Product design + platform engineering
- Timeframe
- 2019–present
- Outcome
- Same interaction model in production seven years later; extended to power agent skills
The problem in 2019
Workato needed a way to let people connect enterprise systems and define what should happen between them, without writing code — and no existing editor model fit that problem well. The original interaction question, stated plainly: how do you make a chain of conditional, data-dependent steps as easy to read and trust as a sentence?
Competing models
Before settling on a linear step-chain, I evaluated a free-form canvas, a form-driven wizard, and a code-first authoring view. Each traded away something the step-chain model kept: a single, always-visible order of operations that technical and non-technical builders could both read the same way.
The principles behind the chosen model
A few principles guided every decision that followed: the structure of a recipe should be readable at a glance, editing one step shouldn't require understanding the whole recipe, and the same model needed to scale from a two-step automation to a business-critical integration touching a dozen systems.
Detailed interaction decisions
How steps connect, how data fields map between them, how conditional branches and loops nest inside a linear list without breaking its readability — these were the actual craft of the editor, worked out one interaction at a time rather than settled by a single big idea.
Edge cases and complex states
Recipes fail mid-run, steps reference data that no longer exists, and people build automations far larger than anyone anticipated in 2019. The editor had to represent all of that without the interface itself becoming the thing that broke.
The editor in 2019 versus today
What changed, what stayed
The visual language, the connector ecosystem, and the surrounding product have all changed substantially since 2019. The core interaction model — a readable, linear chain of steps — has not needed a fundamental redesign to support any of it.
Becoming the execution layer for agent skills
When Workato started giving agents deterministic skills to invoke (see Agent Studio), those skills were existing recipes built in this same editor. The interaction model designed in 2019 for human-authored integrations became, without modification, the execution layer agents call into today.