Schedules
A schedule runs a saved flow automatically on a recurring interval. Schedules run server-side via Vercel Cron, so the flow keeps running even when nobody has the app open.
Modes
| Mode | Meaning |
|---|---|
hourly | Run every N minutes (default 60) |
daily | Run every 24 hours from enabling |
weekly | Run on the weekdays you pick, at the time you pick |
custom | A custom interval in minutes |
Configuring a schedule
Open the flow and choose Schedule runs in the sidebar. Set:
- Mode — hourly, daily, weekly or custom.
- Interval — the minutes between runs (or the time of day for weekly).
- Input — an optional fixed JSON input; the run uses it as the run input every time.
Weekly
Pick the days (Mo–Su) and the time of day. The time is meant in your time zone — the zone is stored with the schedule (shown next to the time field), so “Monday 07:00” stays 07:00 local even when daylight saving shifts.
Mode: weekly
Days: Mo, We, Fr
Time: 07:30
Input: { "region": "Rheinland-Pfalz" } Enabling a weekly plan needs at least one day and a valid time; until both are set the button reads Pick days & time and stays disabled.
You can pause and resume a schedule without deleting it. Switching a schedule to another mode drops the stored days and time.
How it runs
- The cron entrypoint checks for due schedules.
- It starts a run with the configured input.
- The run is attributed to the flow’s owner and billed like a manual run.
Permissions
Only people who can edit the flow may manage its schedule — a viewer cannot make the owner’s flow spend credit.
Example
A tender radar that should go out before the week starts:
Mode: weekly
Days: Mo
Time: 07:00
Input: {} Related
- Webhooks — trigger on demand instead of a timer.
- Run history — scheduled runs appear in the flow’s run history.