Skip to content
Agentic Workflowdocs
v0.9.0Install free

nodes / builtin / trigger

Schedule

Run the flow at a specific time.

Trigger ExtensionWeb app

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

Schedule starts the workflow on the rules you set, while the workflow is On and your browser is open. Each rule picks Run every and then asks only for what that choice needs:

Run every You set
Seconds Every how many seconds (browsers run alarms at most every 30 seconds; below 30, an amber note says so)
Minutes Every how many minutes
Hours Every how many hours and, optionally, Trigger at Minute
Days Every how many days, At (hour), Trigger at Minute
Weeks Every how many weeks, the weekdays, At (hour), Trigger at Minute
Months Every how many months, Trigger at Day of Month, At (hour), Trigger at Minute
Custom (cron) a Cron rule

A new Schedule step starts ready: every day at 09:00. Hours read 12 AM (midnight) and 12 PM (noon); a rule with an hour or minute out of range isn’t scheduled and shows in Ready to run.

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

Hourly, daily, weekly, monthly and cron rules take an optional Timezone (for example Europe/Paris). Empty means your browser’s time. Set one zone for the whole workflow in Workflow settings; a rule’s own zone wins. Schedules stay on the same clock time when daylight saving time changes: a time skipped by the change runs at the first minute after it, a repeated hour runs once.

Custom (cron) takes a 5-part cron rule: minute, hour, day of month, month, weekday. Lists (1,15), ranges (1-5), steps (*/15), names (MON, JAN), L (last day) and shortcuts like @daily work. The field shows the rule in plain words, the next 3 runs (and your own time when the zone differs), and ready-made presets. A 6-part rule with seconds is refused: schedules run at most once a minute. Runs missed while the browser was closed aren’t replayed.

Cron rule
0 9 * * 1-5 every weekday at 09:00
*/15 8-18 * * * every 15 minutes from 08:00 to 18:59
0 8 L * * at 08:00 on the last day of each month
  • Daily reports, digests and reminders.
  • Regular checks: a price, a page, an inbox.
  • Routines that run an agent at set times, with Run agent.
SettingTypeWhat it does
Rules (required)List

Rules changes shape with its Run every choice:

7 choices · pick run every to see its settings

Settings for Seconds

SettingTypeWhat it does
Every how many seconds (required)NumberSeconds between each run. Browsers run alarms at most every 30 seconds, so shorter intervals run every 30 s. For reliable sub-30-second timing, keep the flow running yourself.

Showing settings for Seconds

  • Output

Each output item has these fields:

FieldTypeWhat 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.

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

  1. Schedule with one rule: Days, Every how many days 1, 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.
  • The workflow never runs on its own. Turn the workflow On: schedules only run for workflows that are On, while the browser is open. To test, press Run on the canvas.
  • A seconds schedule runs every 30 seconds. Browsers run alarms at most every 30 seconds, so a shorter interval runs every 30 s.
  • The cron rule is refused. Check it has 5 parts; the message under the field says what’s wrong in plain words.
  • 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.
Edit page

Last updated:

Was this page useful?
Ask Aria about Schedule