Skip to content

cronjobmanager

The module nodes are the building blocks for the flow-based programming. Each node represents a specific task or operation that can be performed by the module. The following table lists the available nodes for this module.

A cron-based trigger node.

  • Name: CronTrigger
  • Tags: trigger, flow, cron, timer, scheduling, automation
  • Category: Trigger
  • Subcategory: Timer > Cron

This node functions as a cron-based trigger, allowing the activation of subsequent nodes based on a cron expression. Cron expressions offer a flexible way to schedule tasks or events by specifying precise times, dates, or intervals (e.g., every minute, daily at midnight, or every Monday at 9 AM). It is ideal for workflows that require scheduled or recurring execution at specific times. The cron configuration is defined in the NodeCronConfig object, where the cron expression is set. This node is essential for automating time-based tasks in flow systems, enabling powerful scheduling capabilities.

Inputs: (0)

  • Trigger : Boolean value that triggers the next node when the cron condition is met. It will emit a true value at every scheduled tick.

The following configuration parameters can be set for this node:

Terminal window
CronTriggerConfig: {
# The cron expression that defines the schedule. Examples include '0 22 * * 1-5' for weekdays at 10 PM, '*/10 * * * *' for every 10 minutes, or '0 0 * * *' for midnight daily.
expression: string,
# The timezone in which the cron job will run (e.g., 'America/New_York', 'Europe/Berlin', 'Asia/Tokyo'). Defaults to UTC if not specified.
timezone: string,
}

Execute a cronjob.

  • Name: ExecCronJob
  • Tags: automation, cronjob, execute
  • Category: Action
  • Subcategory: Execute > Cronjob

This node executes a cronjob on a device. To trigger the node, set the input to true. The output will be a Struct with the cronjob information.

Inputs: (0)

  • Cronjob Status : The status of the cronjob.

The following configuration parameters can be set for this node:

Terminal window
CronjobData: {
# The cron expression defining the schedule, such as "*/10 * * * *" for every 10 minutes.
expression: string,
# The task to run as part of the cronjob (e.g., backup, cleanup, or report).
task: string,
}

Trigger a node at intervals based on the configuration.

  • Name: IntervalTrigger
  • Tags: trigger, flow, interval, timer, automation
  • Category: Trigger
  • Subcategory: Timer > Interval

This node acts as a timer trigger, activating the next node at user-specified intervals. It is especially useful for scenarios where periodic execution is needed, such as polling services, running scheduled tasks, or maintaining heartbeat signals. The trigger can be set to fire at intervals as short as 1 second and up to 1 hour, allowing for flexible time-based automation. The node will continue to trigger the next node at the configured interval until stopped or reconfigured. The interval is defined in the IntervalTriggerConfig object, which allows customization of the time interval in seconds. This node is crucial for workflows that require timed executions, making it a versatile component for flow management and automation.

Inputs: (0)

  • Trigger : Boolean value that triggers the next node when the interval elapses. It will emit a true value at every tick.

The following configuration parameters can be set for this node:

Terminal window
IntervalTriggerConfig: {
# The interval in seconds for the ticker. Default is 5 seconds, with a maximum of 60 seconds.
ticker: int32,
}