Scheduled Task (Cron)
Run an automation at fixed times.
What it does
Fires the workflow according to a cron expression — a compact way to describe schedules like "every weekday at 8:00" or "every 15 minutes" or "on the first of every month". When the time matches, the workflow runs; if it is already running from a previous trigger, the new run is queued.
What you configure
| Field | What it controls | Required | Notes |
|---|---|---|---|
| Cron expression | The schedule. | required | Standard 5-field cron syntax. Example: 0 8 * * 1-5 = weekdays at 8:00. |
| Timezone | Which timezone the expression is evaluated in. | optional | Defaults to the platform's timezone. Use this to keep schedules stable across DST changes. |
| Output name (memory output) | Where the trigger time is stored. | required | The value is an ISO timestamp, useful for naming files or labeling output. |
📷 SCREENSHOT: The Cron Trigger configuration with the expression field, a timezone selector, and a preview of the next three firing times.
Example scenario
Daily team digest. Set 0 7 * * 1-5 (weekdays at 7:00, server time) on a workflow that summarizes yesterday's activity and emails it out before the team arrives.
Recommendations
- ✅ Use a timezone when the schedule matters for human consumers. "8:00 in Berlin" is more meaningful than "8:00 server time", which shifts with DST if the server is on UTC.
- ✅ Test the cron expression by deactivating the trigger and using Manual Run until the workflow itself is reliable.
- ✅ Use specific minutes (
5,25,45) instead of*/15to avoid alignment with other systems' cron jobs that might compete for resources. - ⚠️ If the platform is down at the firing time, the trigger does not catch up retroactively when the platform restarts. The next firing is the next scheduled one.
- ❌ Do not use cron for sub-minute frequencies. Cron resolution is one minute.
What to do next
- To handle one-off external events instead of fixed times: HTTP Webhook.
- To run on a new file: Filesystem Watcher.