Skip to main content

Scheduler trigger

The Scheduler type (CRON on screen) starts a workflow according to a time schedule defined by a five-field CRON expression.

Parameters​

ParameterTypeRequiredDefaultDescription
Time zoneString✅—Zone used to interpret the CRON expression (Europe/Paris, UTC, …).
Cron configString✅—Five-field CRON expression: minute, hour, day of month, month, day of week.

CRON expression​

The CRON expression is made of 5 space-separated values: minute, hour, day of month, month, day of week. Compose it in a few clicks with the generator:

CRON expression generator
Choose a preset or build your expression field by field, then copy it into the Cron config field of the trigger. Click several values in the same field to combine them (e.g. Monday and Thursday, at 4:05 and 4:55).
Presets
Custom expression
Minute
Hour
Day of month
Month
Day of week
0 9 * * *
This expression means: every day, at 09:00.
Next runs:
• Friday, October 16, 2026 at 09:00 AM
• Saturday, October 17, 2026 at 09:00 AM
• Sunday, October 18, 2026 at 09:00 AM
• Monday, October 19, 2026 at 09:00 AM
• Tuesday, October 20, 2026 at 09:00 AM
The next-runs calculation uses your browser's time zone. The trigger interprets the expression in the time zone configured in its Timezone field.

Combined examples

  • Monday to Friday, from 9am to 5pm, every hour: 0 9-17 * * 1-5
  • On the 1st and the 15th of each month at midnight: 0 0 1,15 * *
  • Every working day at 8:30am: 30 8 * * 1-5
  • Every Sunday at 10am: 0 10 * * 0
Validate your expression

Test your expression before deploying to production with crontab.guru or a CRON expression generator.

Input​

The trigger does not receive input data: the execution is triggered only by the time.

Output​

The trigger does not pass business data to the workflow. Only the system variables remain available — see Trigger node.

Errors​

  • Invalid expression — validation is applied on input: an invalid expression is reported explicitly (message "CRON expression not valid") and the trigger cannot be saved until it is corrected. In particular, check:
    • the number of fields: exactly 5 space-separated values;
    • the value bounds: minute (0-59), hour (0-23), day of month (1-31), month (1-12), day of week (0-7);
    • the coherence of the syntax (*, */n, n-m, n,m, n).

Example​

Daily report: create a Scheduler trigger with the expression 0 9 * * * (every day at 9am, Europe/Paris time zone), associate a workflow that retrieves the previous day's data, generates a report and sends it by email. After deployment, the workflow runs automatically at the scheduled time.

See also​