Prerequisites: Basic workflow editing. Familiarity with workflow lifecycle (Active state required for schedules).
Run a workflow automatically every night — useful for reports, sync jobs, and housekeeping without manual triggers.
Goal
At 02:00 Europe/Bucharest daily, fetch data from an API, write a summary to a log, and update a global variable with the last run time.
Step 1 — Cron Schedule trigger
- Create a new workflow and add Cron Schedule as the only trigger.
- Inspector:
- Cron Expression —
0 2 * * *(02:00 every day). - Timezone —
Europe/Bucharest(or your IANA zone). - Description —
Nightly sync.
- Cron Expression —
Five-field order: minute, hour, day-of-month, month, day-of-week. See Cron Schedule reference.
Step 2 — Build the job body
- Add HTTP Request — GET your data source.
- Add Transform or Log to record row count or status.
- Add Write Variable — set global key
lastNightlySyncto{{$now}}.
Step 3 — Dry Run and validate
- Dry Run simulates the graph; the cron timer does not fire during dry run.
- Fix validation errors, then Activate the workflow.
Step 4 — Monitor schedules
Open Jobs panel:
- History — past scheduled runs.
- Schedule — upcoming cron fires for Active workflows.
- Failed — retries and dead-letter review.
- Variables — confirm
lastNightlySyncupdated.
See Jobs Panel for tab details.
Common cron examples
| Expression | Meaning |
|---|---|
0 * * * * | Every hour at :00 |
*/15 * * * * | Every 15 minutes |
0 9 * * 1-5 | Weekdays at 09:00 |
0 0 1 * * | First day of each month at midnight |
Tips
- Long-running jobs: add timeout handling on HTTP nodes and log duration.
- Use Approval gates only when the nightly job performs dangerous actions.
- On runtime agents, cron is embedded in the export manifest and runs headless.