Schedule

trigger.schedule Input v0.1.0

Fires on a cron schedule or fixed interval, emitting a tick with the fire time.

Ports

This is a trigger — it starts runs and takes no input wire.

Direction	Port	Label
Output	`output`	Tick

Properties

Property	Type	Default	Description
Trigger on `mode`	`select`	`"cron"`	Fire the workflow on a cron schedule, or on a fixed repeating interval. `croninterval`
Cron expression `cron`	`cron`	`"0 9 * * *"`	Standard 5-field cron — minute, hour, day-of-month, month, day-of-week — evaluated in the timezone below. Shown when `(mode ?? "cron") !== "interval"`
Run every (seconds) `intervalSeconds`	`int`	`60`	How often to fire, in seconds. Minimum 1. Shown when `(mode ?? "cron") === "interval"`
Timezone `timezone`	`string`	`"UTC"`	IANA timezone the schedule is evaluated in (e.g. UTC, America/New_York).

Examples

Poll a feed every minute (the shipped RSS Digest demo)

{
  "id": "tick",
  "type": "trigger.schedule",
  "config": { "mode": "interval", "intervalSeconds": 60, "timezone": "UTC" }
}

…feeding RSS Read with onlyNew: true — schedule + RSS’s seen-item dedupe is the standard poller pattern: each tick emits only items it hasn’t seen before.

Every weekday at 9am, New York time

{ "mode": "cron", "cron": "0 9 * * 1-5", "timezone": "America/New_York" }

Standard 5-field cron — minute, hour, day-of-month, month, day-of-week — evaluated in the configured IANA timezone. The editor validates the expression live.

Tips

In the editor, a schedule doesn’t tick on its own — Test workflow fires it once so you can develop without waiting for 9am. Deployed apps run the schedule for real, per the production trigger model.
Timezone matters twice a year: 0 9 * * * in America/New_York stays 9am local through DST; the same cron in UTC shifts an hour.
For run-once batch jobs triggered by an external scheduler (cron, CI), use the Manual trigger and job mode instead — the app executes once and exits.

This page is generated from the node registry by gen-node-docs.mjs on every site build — ports, properties, defaults and visibility rules cannot drift from the code. The examples above are hand-authored and merged in.