Schedule (Cron)
Trigger · Stable
Run on a recurring schedule using a cron expression and timezone.
5-part cron expression (e.g. ‘0 8 * * 1-5’ for weekday 8am). Timezone must be a valid IANA zone (e.g. ‘Europe/Prague’). Missed fires older than two scheduler ticks (>120 s) are skipped. Ideal for daily digests, periodic contact sweeps, and scheduled data pulls.
When to use
Section titled “When to use”Use when the workflow must run at a fixed cadence regardless of external events — daily digest emails, weekly contact sweep, nightly data pull. The flow injects no trigger data; use Set values or module inputs to seed context at run time.
When not to use
Section titled “When not to use”If the flow should react to data pushed by an external system, use Webhook or Event. If it should fire once when a human decides, use Manual. For single-run future delays inside a flow, use the Wait step. Heads-up: a scheduled run has no signed-in user; {{ user.* }} / {{ actor.* }} fall back to the workflow’s creator (and are empty if it has none), NOT the operator watching the run. Bind a concrete email / actor_id when you mean someone other than the creator.
Inputs
Section titled “Inputs”expression
Section titled “expression”string · required
5-part POSIX cron: minute hour day-of-month month day-of-week, evaluated in the timezone below (not UTC). Missed fires older than two scheduler ticks (>120s) are skipped rather than fired late.
Example: 0 8 * * 1-5
- ✓
0 8 * * 1-5— weekday mornings at 8:00 — a daily digest - ✓
*/15 * * * *— every 15 minutes — a frequent sweep - ✗
8:00 daily— not cron syntax — use the 5-field form, e.g. “0 8 * * *”
timezone
Section titled “timezone”string · optional
An IANA timezone name the expression above is evaluated in — determines when “8am” actually fires, including DST transitions.
Example: Europe/Prague
- ✓
Europe/Prague— CET/CEST with DST handled automatically - ✓
UTC— no DST shifts — good for infra-facing schedules - ✗
CET— a fixed-offset abbreviation, not an IANA zone — does not observe DST; use Europe/Prague instead
enabled
Section titled “enabled”bool · optional
Whether the schedule is currently armed. Turn off to pause a recurring flow without deleting its trigger configuration.
Example: true
- ✓
true— schedule fires normally - ✓
false— schedule is paused — no runs until re-enabled - ✗
"yes"— must be a real boolean, not the string “yes”
Auto-generated from the skill registry (load_skills()). Do not edit by hand.