Cron

The Cron component can be used to schedule messages based on specific moments in time. It uses cron tabs to indicate when to send a message into the flow.

The component can configure jobs in the settings or uses an incoming message that holds jobs as a key. The value should be an array of strings. When configuring jobs in the settings, the component stays in a waiting state until a message is received. This will trigger execution of the jobs configured and the component will have a Running state. Sending multiple messages to the component will cancel and overwrite previous jobs. When multiple jobs are required, add them as multiple items in the jobs array of the message (see examples).

Note

When using settings to configure multiple jobs, use a , as separator for the different jobs.

Configuration

Cron Jobs

The list of jobs with their respective cron tabs, and the message they output.

Syntax:cron tab | data (only string supported) | comment

Examples: */5 * * * * *| ping - Will send the message ping every 5 seconds.

Cron tab:

┬ ┬ ┬ ┬ ┬ ┬
│ │ │ │ │ │
│ │ │ │ │ └─ day of week (0 - 7) (0 or 7 is Sun)
│ │ │ │ └─── month (1 - 12)
│ │ │ └───── day of month (1 - 31, L)
│ │ └─────── hour (0 - 23)
│ └───────── minute (0 - 59)
└─────────── second (0 - 59, optional)

Some examples:

tab	description
0 0 1 1 *	Run annually, at First of January at 00:00
0 0 1 * *	Run once a month, at 00:00 on the first day of the month
0 0 * * 0	Run once a week, at Sunday 00:00
0 0 * * *	Run once a day, at 00:00
0 * * * *	Run once an hour, at XX:00
*/5 * * * *	Run once every 5 minutes

Inputs | Outputs

Cron

Input

Output

00 0 (ilsy35hs)

Any message that is sent to the Cron component will set it to a running state. This is needed to trigger jobs that are set using the settings. When using jobs in the incoming message it will be triggered instantly when the message comes in, an example with multiple jobs could be:

{
  "jobs": ["*/5 * * * * *| ping1", "*/3 * * * * *| ping2"]
}