Scheduled flows
A flow can run by itself: every few minutes, or on a cron schedule in your time zone. Use it to send a daily summary, refresh data from an API, or work through a queue.
Set a schedule
Ask the assistant (“run the sync flow every hour”) or, as an admin, use set_flow_schedule:
{ "name": "sync", "every_minutes": 60 }
{ "name": "digest", "cron": "0 7 * * mon-fri", "timezone": "America/New_York" }every_minutes: 5 or more. Orcron: five fields with*, lists, ranges,/steps, month and weekday names, or@hourly,@daily,@weekly,@monthly. Runs are at least 5 minutes apart. The time zone defaults to UTC.input: what the flow sees as{{input.*}}.- One schedule per flow, up to 10 per site.
How runs work
- Each run may take up to 60 seconds. A run is skipped while the previous one is still going.
- There is no visitor, so there are no cookies; spam protection doesn't apply.
- A run fails when the flow answers with status 400 or more, errors, or runs out of time. End your flow with
respondand a status so failures show. - After 5 failures in a row the schedule pauses itself and the site's billing owner gets one email. Fix the flow, try Run now, then Resume.
- Archived sites don't run schedules.
Manage schedules
The site's Forms & flows page lists every schedule with its last and next run, Run now, Pause/Resume and Remove. The tools are list_flow_schedules, pause_flow_schedule, resume_flow_schedule, run_flow_schedule_now and delete_flow_schedule. Deleting a flow deletes its schedule.
Recipe: working through a queue
Forms add jobs to the record store with status: "pending"; a scheduled flow claims a few per run with a conditional update (if status = pending, set working), processes them, and marks them done. The claim makes it safe when a run and a form, or two runs, overlap.
Price
Each run is one flow call: 3.01 credits per 1,000. A flow every 5 minutes is about 8,640 runs a month, roughly 26 credits.