Automation Studio
Describe a business process in plain language and get a typed, editable workflow that runs with retries, approvals and full logs.
Open the evaluation boardProblem
No-code automations fail silently, and one-off scripts have no retries, no audit trail and no owner.
Try it live
Ask for this: when a wholesale order over €500 arrives, check stock, alert the roastery on Slack and email the café an ETA. Edit the generated graph and run it with a test order. Then make a step fail and watch the retries, the dead-letter queue and the one-click replay.
Proves
Workflow engine design, end-to-end type safety, and side effects that run exactly once.
Signal chain
- describe
- typed graph
- validate
- version
- queue with retries
- idempotent actions
- replay
Stack
Node · TypeScript · BullMQ + Redis · Postgres · Zod · Vue Flow
Engineering highlights
- One Zod schema validates the model’s output, the API payload and the editor form.
- Side effects run once, even on retry, through idempotency keys and an outbox table.
- Workflows are versioned, and every run can be replayed step by step.
| Operating limit | Value |
|---|---|
| Workflow runs per visitor per day | 10 |
| Connectors | Sandboxed mocks |
| Retries | 3, exponential backoff |
| Model calls per workflow (est.) | 1–3 |
Status The evaluation board for this part is open. It starts on curated samples, and your own text runs live within your daily allowance. Open the evaluation board