Workflow automation
Flowline
A canvas for approvals and hand-offs that used to run through email.
- Platforms
- Desktop web
- Engagement
- All delivered under NDA to private clients, who own what we built. Screens are representative: no client names, no user data.
Built for an operations team whose approval chains passed through a shared mailbox. Every request now has a visible state and a named owner.
The problem
An approval that lives in email loses its state. Nobody could say which request was waiting on whom without reading a thread, and a stalled request left no trace of where it stopped.
What we decided
Steps are placed on a canvas in the order they run, joined by connectors.
A condition step shows its field, operator and value in a panel beside the canvas.
Approval steps name the person or role responsible, so a waiting request has an owner.
Run history records every step with its time and result.
A failed run restarts from the step that failed, not from the beginning.
Screens