Flow reference: Triggers
Schedule (cron)
Runs on a schedule (cron): every hour, every Monday at 9:00, every 15 minutes…
Runs on a schedule (cron): every hour, every Monday at 9:00, every 15 minutes…
When and how to use it
Add this trigger to the appropriate flow; it has no incoming execution connection.
Configure its filters and identifiers below.
Connect an output to the action that should respond to this event.
Configuration fields
Cron expression — cron
Five fields: minute hour day-of-month month weekday. Example: /15 runs every fifteen minutes; 0 9 * 1-5 means weekdays at 09:00 in the selected timezone.
Input: Text.
Editor guidance: minute hour day month weekday — e.g. /15 (every 15 min), 0 9 * 1-5 (weekdays 9:00).
Format example, not a ready value for your server:
0 9 * * 1.Default:
0 * * * *.Time zone (blank = UTC) — timezone
Choose the timezone used to interpret the schedule, for example Europe/Warsaw. Daylight-saving changes can alter the corresponding UTC time.
Input: Text.
Format example, not a ready value for your server:
Europe/Warsaw.Default: ``.
Outputs and next steps
out: Continue to the next step.Test and troubleshoot
Invoke the correct trigger with simple inputs and verify the expected effect. Confirm variables exist on this path. A preview alone does not verify Discord delivery.
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).
Save, validate and publish. Perform one real test and read the first relevant log error. [Testing](/docs/flow-testing) · [Variables](/docs/flow-variables) · [Permissions](/docs/flow-permissions).