Cron jobs and scheduled tasks
A schedule runs a workflow on a clock, whether or not anyone visits. The pool league template uses one to pull new results every morning; other sites rebuild a summary every hour or send a digest on Mondays.
Free includes one daily scheduled job. Pro has 10 that can run every 15 minutes, Agency 50 that can run every minute.
Pick the simple kind, every so many minutes or hours, or a calendar time in the timezone you choose. Daylight saving is handled, and the editor shows the next few run times as you type, so you can see that "9am Mondays" means what you think it does.
Try it
The cron field from the schedule editor
Timezone
Examples
Schedule (cron)
Next runs load in your timezone.
The next 7 days
How it works
- 01
Point it at a workflow
A schedule runs one workflow. If that workflow takes input, you set the values once and they're sent on every run.
- 02
Test it with Run now
Switch it on and it fires by itself. Run now fires it on the spot, and each run lands in the schedule's history with how it went.
Questions
How often can a schedule run?
That depends on the plan. Free includes one scheduled job that runs daily, Pro allows 10 at up to every 15 minutes, and Agency 50 at up to every minute.
What if a job needs more than one run?
Run it as a chain. Each run saves a bookmark and the next carries on from it in the background.
Under the hood
The technical details
- mode: interval
- Every N minutes or hours, timezone-independent. every >= 1.
- mode: cron
- A standard 5-field cron expression evaluated in an IANA timezone, with daylight saving handled. The editor previews the next runs.
- input
- A fixed input passed as $input on every fire, edited as a form built from the workflow's input schema.
- workflow
- A versioned reference, @published or @latest; a bare slug means @published.
{
"workflow": "reports/daily-summary@published",
"mode": "cron",
"cron": "0 9 * * 1",
"timezone": "America/New_York"
}Related features
Run a schedule now
Fire a schedule on the spot to test it, without waiting for its next turn. You can switch it on or off whenever you like.
Jobs longer than one run
A scheduled job that's too big for one run, like working through thousands of records, can run as a chain. Each run saves a bookmark and the next one starts from it.
Run history and step traces
Each run is listed with how it went. Open one to see the steps, what each read and what it got back, and your AI can read the same history to debug its work.
Cron, timezone, color and slug fields
A cron field shows the expression in words and lists the next few run times. Timezone and color pickers are built in, and a slug field fills itself in from the title.