Workflows and automations
Automations you describe in a sentence.
A workflow is a standing instruction. You describe it once, in plain language, and Suvi runs it on schedule.
Every Monday at 9, list unpaid invoices and send polite reminders. Show me before anything goes out.
Suvi compiles that into a validated definition: a trigger, a sequence of steps, and an approval gate. You can see the compiled version before it runs.
Triggers
- Manual. You run it.
- Once. At a specific time.
- Cron. On a repeating schedule, in your timezone.
- Event. When something happens, such as an invoice going overdue.
No model in the run loop
The compilation step uses a model. The execution does not. Once a workflow is defined, running it is deterministic: the same trigger produces the same steps in the same order every time.
This is the difference between a workflow and asking Suvi to do something. Asking is flexible and varies. A workflow is repeatable and auditable, with a log of every run.
Approval gates
Any step that sends, pays or changes something outside Suvi can pause for you. Approval arrives as a card in chat.
When a reminder is the better answer
If the thing you want is "tell me to do X on Friday", use a reminder rather than a workflow. Workflows carry setup cost and a log you will not read. Reserve them for work that actually recurs.
Proactive offers
When Suvi notices you doing the same thing repeatedly, it offers to automate it. You can decline, and declining is remembered.