Blocks
Schedule
The schedule trigger: cron expressions with a timezone — run workflows every morning, every 30 minutes, or every Friday at 4.
Time as a trigger: a cron expression plus a timezone.
When it runs
Whenever the cron matches, while the workflow is active. Common shapes:
| cron | meaning |
|---|---|
0 9 * * 1-5 |
weekdays at 9:00 |
*/30 * * * * |
every 30 minutes |
0 16 * * 5 |
Fridays at 16:00 |
0 8 1 * * |
the 1st of each month, 8:00 |
Config
Cron + timezone. The five fields: minute, hour, day-of-month, month, day-of-week.
- Cron — standard five-field syntax.
- Timezone — IANA name (
America/Los_Angeles); the cron is evaluated in it, DST handled.
Output
An empty object {} — like manual, a scheduled run starts with no
input. First stop is usually a web request or store read.
Patterns
- Digests — morning brief, weekly recap: schedule → fetch → AI summarize → deliver.
- Monitors — every-30-minutes fetch → filter new/worthy → notify only when something changed.
- Housekeeping — nightly cleanup against a store.
Gotchas
- Deactivating stops the clock; re-activating resumes it. Missed windows don't back-fill.
- For "once per new item" semantics on a polled API, use watch — a raw schedule re-processes the same items every tick unless you dedupe yourself.