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
POSIX cron syntax — minute hour day-of-month month day-of-week.
timezone
Section titled “timezone”string · optional
IANA zone, e.g. Europe/Prague.
enabled
Section titled “enabled”bool · optional
Auto-generated from the skill registry (load_skills()). Do not edit by hand.