Scheduled
Use the Start Scheduled node to run a flow on a recurring interval, a weekly weekday and time, or a one-time timestamp, with an IANA timezone.
Scheduled
Start Scheduled (startScheduled) is a start node. Drop it on the canvas instead of Start when the platform should fire the flow without an API call or webhook.
A flow still has a single start node. You cannot combine scheduled and manual starts on the same graph.
Configure
Select the Start Scheduled node. The sidebar exposes:
| Field | Use |
|---|---|
| Schedule type | Recurring, Weekly, or One-time |
| Interval | Recurring only: value plus unit (Minutes, Hours, or Days) |
| Weekday and time | Weekly only: ISO weekday plus hour and minute in the chosen timezone |
| Run at | One-time timestamp |
| Timezone | IANA name such as UTC or Europe/Istanbul |
Runtime persists a cron expression for recurring and weekly, or runAt for one-time. Missing both a schedule and runAt fails the start node.
After it fires
Each tick creates a run with triggerSource schedule. Inspect executions in Run History.
To also start the same logic from code, prefer a Start node plus API, or keep a scheduled flow and a separate API flow.
Examples
- Recurring: every 1 day at the configured timezone, pull yesterday's rows and email a summary.
- Weekly: every Monday at 09:00
Europe/Istanbul. - One-time:
runAtfor a launch checklist that should not repeat.
Related
- Manual for on-demand runs
- API to trigger a non-scheduled graph from your backend
- Usage & Cost before a high-frequency interval