On a schedule
Every Monday at eight. The first working day of the month. The last Friday of the quarter. It runs whether or not anyone remembers.
The routine that
never slips.
The Monday report, the invoice run, the compliance check, the renewal watch. Describe the process once and it runs on schedule or on trigger — with the same approval gates as everything else.
On a schedule, or when something happens.
When mail arrives
A new enquiry, a purchase order, a supplier invoice — the message itself starts the process that handles it.
When something changes
A job marked complete, a payment received, a form submitted, a date approaching — the change is the trigger.
When you ask
Some processes should run when you say so. Same workflow, started by hand, with the same record of what it did.
Described, not drawn
No canvas. No boxes and arrows.
Write down what the process does the way you would explain it to a new starter, and Kaer turns it into a workflow you can inspect and change. When the process changes, you edit the description — not a diagram.
- Plain-English description in, running process out
- Every step visible before you turn it on
- Change the wording; the process follows
01$ kaer automation · nightly-report
02trigger 02:00 · fetch metrics · render summary
03connected · postgres · slack · gmail
04approval gate — send to #team?
05✓ approved on phone · report delivered
06next run scheduled · tomorrow 02:00
07audit log · every action attributed
01$ kaer automation · nightly-report
02trigger 02:00 · fetch metrics · render summary
03connected · postgres · slack · gmail
04approval gate — send to #team?
05✓ approved on phone · report delivered
06next run scheduled · tomorrow 02:00
07audit log · every action attributed
Gates stay gates
Automatic does not mean unattended.
A running workflow obeys the same rules as anything else Kaer does. The report files itself. The invoice waits. The page waits. If a step fails or something looks wrong, it stops and tells you rather than carrying on.
- Approval steps inside the workflow, not bolted on after
- Failures surface with the detail attached, not silently retried forever
- A record of every run: what ran, what changed, who approved
Automate the thing you do
every single week.
Start from a template or describe your own. Both take minutes.
or browse templates