CLK
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.
DailyWeeklyMonthly
01The run
You describe it once. It runs itself.
01
MON 08:0002
MAILBOX03
RECORDS04
DRAFT05
APPROVAL06
SENT07
LOGGEDA workflow run, in order: Trigger: every Monday at 08:00; Read last week's mailbox; Pull the numbers from your records; Draft the report; Hold for your approval; Send it to the list; Record what the run did.
02Triggers
On a schedule, or when something happens.
MSG
When mail arrives
A new enquiry, a purchase order, a supplier invoice — the message itself starts the process that handles it.
Inbox trigger
EVT
When something changes
A job marked complete, a payment received, a form submitted, a date approaching — the change is the trigger.
EventThreshold
MAN
When you ask
Some processes should run when you say so. Same workflow, started by hand, with the same record of what it did.
On demand
03Described
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
04Gates
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.
