Triggers, conditions and steps
A trigger starts an automation, conditions decide if it goes ahead, and steps do the work, one after the other.
Triggers: what starts it
| Trigger | Example |
|---|---|
| An entry is created in a collection | You log “Morning run, 5.2 km” in Workouts. |
| A value changes, from one value to another | Done becomes ticked. Status changes to Finished. |
| A date arrives | The Due date is today. 3 days before a birthday. |
| A schedule | Every Sunday at 20:00. Every morning at 7:00. |
| A button or a command | A “Plan my week” button on a card, a command in search, kzx run, or Run now. |
| Data comes in | A connector, such as Google Health (stage 6), delivers last night’s sleep. |
| Everything is done in a view | You tick the last open habit of today. |
Every option of every trigger is in Triggers.
Replays never start automations. These things only repeat what already happened, so they start nothing: the one-time import from the old Kaizendex app, a restore from your folder or a backup, sync catching a device up, Undo and Redo, and restoring an old version.
Conditions: if this is true
A condition is a short rule in the app’s one expression language, for example
@Done == true. If the condition is false, the automation stops and does nothing. Conditions
are optional.
Steps: what it does
Steps run in order. A step can be:
- an everyday action: set a value, add a tag, create an entry from a preset, notify you, ask the AI, call a website you approved. The full list is in Actions.
- a branch:
ifandchooserun different actions for different cases (“if Distance is over 10 km, add the tag Long run”). - a wait: until a time, or for a while (“wait 2 hours”).
- a Script step: a small TypeScript program. See Scripts.
A script’s results can feed the everyday actions after it.
A wait splits the run
The steps before a wait are one run. The app applies them. After the wait, the remaining steps run as a new run that reads fresh data. So a wait never works on old values.
On Pro, waits are kept in the cloud (part of Cloud Sync), so they end on time while your devices are off. On Free, a wait that ends while the app is closed goes on the next time you open the app.
Run modes: two starts at once
A run mode decides what happens when an automation starts again before it has finished. It counts per automation and per entry.
| Mode | What happens | Default for |
|---|---|---|
queue |
New runs for the same entry wait their turn, up to 10. Tick two habits fast and it runs for both. | entry created, value changes |
single |
If it is already running, a new start is skipped. | schedules, buttons |
Time zones
Every schedule and date automation has its own time zone. By default it is your home zone on the day you make it. “Now” and “today” use that zone.
- A time that does not exist on a daylight-saving day (02:30 when clocks jump forward) runs at the next valid minute.
- A time that happens twice (when clocks go back) runs once.
- When you travel, the automation stays in its own zone, unless you pick follow where I am.