Automations
Automation trigger reference
Review schedule, data-change, and heartbeat trigger settings and use cases.
A trigger controls when a workflow starts. A list step controls which rows it processes.
Trigger selection examples
| Operating situation | Recommended trigger | Reason | Measure |
|---|---|---|---|
| Create a report at a fixed daily time | cron | The operating rule depends on a time. | On-time runs, delay, and failures |
| Start work after a new reservation | db | One data change needs an immediate response. | Runs per change and duplicates |
| Find reservations 30 minutes after start | heartbeat | Each signal checks current time and status again. | Selection delay, missed rows, and repeats |
Do not review run count alone. Compare it with the number of work targets. A poor query can miss required records or process the same record repeatedly.
cron
Starts on a configured cron schedule.
schedulecontains the cron expression.- Use it for daily cleanup, reports, and work at a fixed time.
0 3 * * *starts every day at 03:00.- Saving an active workflow synchronizes its schedule.
db
Starts when a row is inserted, updated, or deleted in allowed data.
source_tableselects the watched data.source_eventusesinsert,update, ordelete.- Steps reference the changed row through
${trigger}. - Use it for one immediate reaction to a new reservation or customer.
heartbeat
Starts on the shared platform heartbeat.
- It does not need a separate schedule for each workflow.
- The first step finds current rows with time and status conditions.
- Use it for no-shows, old pending reservations, and stale conversations.
- The next heartbeat repeats the query after a missed signal.
manual
A run record can show manual as its source. A workflow definition uses cron, db, or
heartbeat as its operating trigger.
Read Runs and repeat safety for behavior after a trigger starts.