DocsNodesStarts the workflowSchedule

Schedule

Starts a run on a timetable: every few minutes, every hour, every day at a time, on chosen days, or on any cron expression. Times are in UTC.

Kindtrigger:schedule
GroupStarts the workflow
CreditsFree
Ports out1

How it looks

Settings

SettingRequiredWhat it does
RepeatcronYesPick every N minutes, hourly, daily, weekly or monthly and the console writes the cron expression for you, or type your own, like 0 6 * * * for 06:00 UTC each day. Next runs shows when it will fire.
Correlation keycorrelationKeyNoWhich runs count as the same for the setting above. Left empty, each occurrence is its own. Set it to share one line with another trigger.

Ports

PortThe run leaves by it when
defaultAt each scheduled time.

What it adds to the run

Later nodes can read these, in a condition or as {{name}} in a text field.

ValueHolds
triggeredAtWhen the trigger fired.

Example

Water the plants at dawn

  1. Repeat daily at 05:30 UTC.
  2. Connect Send to client with command pump.run and payload { "seconds": 20 }.
If WBSKT was downOccurrences missed while the engine was restarting are fired one after another when it's back, so nothing is skipped.

Problems you might see

CodeMeans
INVALID_CRONThe cron expression can't be read. The console checks it as you type.

Problems found when you publish stop the publish and point at the node. Problems while a run is going fail the node, and its On failure setting decides what happens next. See the error codes for the API's own.