The Cronjob Management Plugin is your all-in-one solution for task scheduling and automation, built to empower system administrators and developers alike. From streamlining repetitive operations to executing commands on multiple devices, this robust plugin makes managing cronjobs a breeze.
Take control of your task automation today! Elevate your operations with the Cronjob Management Plugin and experience the future of scheduling. ⏰✨
| Field | Value | |-----------------------|---------------------------------------------------------------------------| | NAME | cronjobmanager | | VERSION | 1.0.0 | | ALIAS | Cronjob Management | | TAGS | control, automation, task scheduling, cronjob, management | | SHORTDESCRIPTION | Manage and execute tasks using cronjobs for automated operations. | | DESCRIPTION | The Cronjob Management plugin allows managing and automating tasks using cronjobs. It provides an intuitive user interface for scheduling tasks, executing commands on devices, and monitoring real-time command execution. Key features include creating, editing, and deleting cronjobs, starting and stopping cronjobs, viewing cronjob logs, and providing widgets for a clear overview and execution of cronjobs. Additionally, the plugin offers various flow nodes, such as "Execute Cronjob" and interval triggers, that trigger flows at specified intervals. With seamless integration capabilities, the Cronjob Management plugin simplifies task scheduling and enables automated operations for system administrators. |
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.
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.
true
value at every scheduled tick.The following configuration parameters can be set for this node:
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.
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.
The following configuration parameters can be set for this node:
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.
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.
true
value at every tick.The following configuration parameters can be set for this node:
IntervalTriggerConfig: {
# The interval in seconds for the ticker. Default is 5 seconds, with a maximum of 60 seconds.
ticker: int32,
}