At a glance
- Fires when
- An interval elapses, or a chosen weekday reaches a set time
- Emits
- Timestamp, plus the interval or the calendar rule
- Two modes
- On an interval · On a calendar schedule
Set it up
A new Schedule node opens on a calendar schedule — weekdays at 7:00 AM — which is the right shape when the flow belongs to a moment in your day. Switch Schedule Type to On an interval when the cadence is "every N" and the wall-clock time does not matter.
Configure
| Field | Default | What it does |
|---|---|---|
| Schedule Type | On a calendar schedule | Interval, or chosen weekdays at a set time. |
| Interval | Every 5 minutes | 5s, 30s, 1m, 5m, 15m, 1h, or Custom. Interval mode only. |
| Custom Interval (seconds) | 60 | The interval in seconds, when Interval is Custom. |
| Days | Weekdays | Day chips — tap them, or use the Every day / Weekdays / Weekends quick-sets. Calendar mode only. |
| Time | 7:00 AM | The local time of day to fire at. One time per node. Calendar mode only. |
| Custom Arguments | — | Extra key-value pairs merged into the payload. |
Output
Every key is available downstream as {{key}}.
| Key | Type | Value |
|---|---|---|
timestamp | String | When the fire actually happened, ISO 8601 |
interval | String | Interval mode: the configured interval |
scheduledFor | String | Calendar mode: the occurrence this fire represents, ISO 8601 |
schedule | String | Calendar mode: the rule in words — Weekdays at 7:00 AM |
catchUp | Boolean | Calendar mode: true when this fire makes up a missed occurrence |
Example: a weekday morning briefing
Schedule fires at 7:00 AM Monday to Friday. Template writes the line from {{schedule}}. Notification delivers it.
Paste this into the Flow Builder to get the same flow:
Every weekday at 7am, send me a notification with my morning briefing.
Good to know
A missed morning is made up once. If the Mac was asleep when a calendar occurrence passed, the flow fires at the next wake or launch with catchUp true and scheduledFor set to the miss. Five slept-through mornings still produce one fire, not five. Gate on {{catchUp}} when a late delivery would be worse than none.
Turning a flow off is not a miss. Disabling it, re-enabling it, or editing the schedule resets the baseline to now, so nothing stale arrives on the way back.
8 AM stays 8 AM across daylight saving. A nonexistent spring-forward time fires at the next valid instant; a repeated fall-back time fires once.
One node is one day set at one time. Want 7 AM and 7 PM? Add a second Schedule node — both can feed the same flow. Monthly and cron-style rules are not expressible here; use interval mode.