Schedule

Run the workflow automatically at set times: every few minutes, daily at 9:00, every Monday, on the 1st of the month.

What it does

Schedule starts the workflow on the rules you set, once the workflow is published. Each rule picks a Trigger Interval and then asks only for what that interval needs:

Trigger Interval	You set
seconds	Seconds Between Triggers (at least 10)
minutes	Minutes Between Triggers
hours	Hours Between Triggers and, optionally, Trigger at Minute
days	Days Between Triggers, Trigger at Hour, Trigger at Minute
weeks	Weeks Between Triggers, the weekdays (field Units), Trigger at Hour, Trigger at Minute
months	Months Between Triggers, Trigger at Day of Month, Trigger at Hour, Trigger at Minute

Add several rules to combine schedules, for example weekdays at 9:00 plus Saturdays at noon.

Daily, weekly and monthly schedules (and hourly ones pinned to a minute) stay on the same local clock time when daylight saving time changes.

When to use it

• Daily reports, digests and reminders.
• Regular checks: a price, a page, an inbox.
• Routines that run an agent at set times, with Run agent.

Inputs and settings

Setting	Type	What it does
Rules REQ(required)	List

Rules changes shape with its Trigger Interval choice:

6 choices · pick trigger interval to see its settings

secondsminuteshoursdaysweeksmonths

Settings for seconds

Setting	Type	What it does
Seconds Between Triggers REQ(required)	Number	Seconds between each run. Note: the browser floors alarms at ~1 minute, so second-level schedules are best-effort — the minimum is 10s and short intervals are effectively rounded up to about 1 minute. For reliable sub-minute timing, keep the flow running yourself.

Showing settings for seconds

Outputs

• Output

Each output item has these fields:

Field	Type	What it holds
scheduled	Always true

Shape of an output item

{
  "scheduled": true
}

Schedule only sends { "scheduled": true }. It carries no date or other context; use Get Current Date when the next steps need the time.

Dependencies and credentials

None. This node needs no connection and has no slots for other nodes.

Example workflow

1. Schedule with one rule: days, Days Between Triggers 1, Trigger at Hour 8 AM, Trigger at Minute 0.
2. RSS Feed Read fetches a feed.
3. Limit keeps the 5 newest posts.
4. Telegram sends them to you.

Common issues

• The workflow never runs on its own. Publish the workflow: schedules only run for published workflows. To test, run it from the canvas.
• A seconds schedule runs about once a minute. The browser runs scheduled alarms at most about once a minute, so second-level schedules are approximate. The minimum is 10 seconds.
• A monthly schedule skipped a month. That month has no such day (for example the 31st). Pick a day that every month has, such as the 1st or the 28th.

Related nodes

• When Started: run the workflow by hand.
• Browser Startup: run when the browser opens.
• Get Current Date: add the time to the data.
• Run agent: give a scheduled task to an agent.