Triggers
Every automation has exactly one trigger. A trigger is always written as settings (JSON). How triggers fit in: Triggers, conditions and steps.
All triggers
| Trigger | Options | Example | Runs where | Default run mode |
|---|---|---|---|---|
| An entry is created | the collection | a new workout is logged | the device that made it | queue |
| A value changes | the collection, the property, “from” and “to” | Done becomes ticked; Status changes to Finished; Route stops recording | the device that made the change | queue |
| A date arrives | the entry’s own Entry date or a Date property; how long before it; the time zone | the Due date is today; 3 days before a birthday | Cloud Sync (Pro) or your one device (Free) | not decided yet |
| A schedule | the time, the repeat, the time zone | every Sunday at 20:00 | Cloud Sync (Pro) or your one device (Free) | single |
| A button or command | a card button, a command in search, kzx run, or Run now |
a “Plan my week” button | where you pressed it | single |
| Data comes in | the source: the webhook inbox or a connector | Google Health delivers last night’s sleep | Cloud Sync (Pro) or your one device (Free) | not decided yet |
| Everything is done | the view | the last open habit today is ticked | Cloud Sync (Pro) or your one device (Free) | not decided yet |
On Pro, “Cloud Sync” in this table means your cloud box: your own small private database in the cloud, which runs these triggers while every device is off. Free has Cloud Sync for one device, but no cloud box, so on Free these triggers run on your one device, while it is on.
An automation may read an end-to-end encrypted collection (only your devices hold the key). If the cloud box has no key for it, these triggers run on one of your devices instead, picked by the cloud box.
A recording starts it once
A JSON property can record live from a phone sensor, such as the Route of a run. See JSON.
- While it records, A value changes does not start for each new point.
- It starts once, when the recording stops. The editor shows it as “When Route stops recording”.
- Pause and Resume do not start it.
- Editing the route later (removing wrong points) is an ordinary change, and starts it again.
Example: “When Route stops recording → notify me: 5.2 km in 28:00” runs once per run.
A card button can start a recording (“Start run”), but no automation can. Only your tap on the phone starts one.
Data from a webhook
A webhook is a message another service sends to Kaizendex when it has new data, for example Whoop after a sleep sync. The Data comes in trigger can start on it.
- Your webhook address is private to you.
- We check the sender. When a service signs its messages, we check the signature. A message that fails the check is dropped.
- Size and rate limits apply.
- What arrives is data, never an order to the AI. A sleep note that says “delete my Workouts” is saved as text and does nothing.
Run modes
| Mode | Behaviour |
|---|---|
queue |
Runs for the same entry wait their turn, up to 10. |
single |
If the automation is already running, a new start is skipped. |
Run modes count per automation and per entry.
Time zone options
| Option | Behaviour |
|---|---|
| Default zone | your home zone on the day you make the automation |
| A zone you pick | the automation keeps it when you travel |
| Follow where I am | the automation uses the zone you are in |
| A time that does not exist (daylight saving) | runs at the next valid minute |
| A time that happens twice (daylight saving) | runs once |
What never starts an automation
| Event | Why |
|---|---|
| The one-time import from the old Kaizendex app | a replay of the past |
| Restore from your folder or a backup | a replay |
| Sync catching a device up | the change already ran where it was made |
| Undo and Redo | a replay |
| Restoring an old version | a replay |
| An automation’s own change | it never starts itself again |
| A fourth link in a chain | a chain of automations stops after 3 |
Limits on starts
| Rule | Value |
|---|---|
| Runs per hour, per automation | 60, except an approved batch |
| Volume guard | pauses and asks when runs jump far above normal, for example 100 in a minute |
| Big batch | asks once when an import or bulk edit would start it more than 50 times |
| Missed runs caught up | up to 14 days back |