青龙面板[Qinglong] icon

青龙面板[Qinglong]

青龙面板计划任务节点.详细API请参考：https://qinglong.online/api/

Actions64

Overview

This node integrates with the Qinglong Panel API to manage scheduled tasks (cron jobs) and related resources. Specifically, for the "定时任务" (Scheduled Task) resource and the "创建定时任务" (Create Scheduled Task) operation, it allows users to create new cron jobs by specifying details such as the command to run, the schedule in cron expression format, task name, labels, dependencies, and additional scheduling rules.

Common scenarios where this node is beneficial include:

  • Automating repetitive scripts or commands on a server.
  • Managing multiple scheduled tasks programmatically within an automation workflow.
  • Creating complex task chains with pre- and post-task dependencies.
  • Adding metadata like labels to organize and filter scheduled tasks.

Practical example:

  • A user wants to automate a backup script that runs every day at midnight. They can use this node to create a scheduled task with the appropriate cron expression (0 0 * * *), specify the backup command, and add labels for categorization.

Properties

Name Meaning
请求Body JSON object containing the details of the scheduled task to create. It includes:
- command: The command string to execute.
- schedule: The cron expression defining when the task runs.
- name: The name of the task.
- labels: An array of strings representing tags/labels for the task.
- sub_id: Numeric ID for any subtask associated.
- extra_schedules: Array of additional scheduling rules (any type).
- task_before: String indicating a task to run before this one.
- task_after: String indicating a task to run after this one.

The property expects a JSON input structured like:

{
  "command": "string",
  "schedule": "string",
  "name": "string",
  "labels": ["string"],
  "sub_id": 0,
  "extra_schedules": [],
  "task_before": "string",
  "task_after": "string"
}

Output

The node outputs the result of the API call in the json.result field of the first item in the output data array. This typically contains the response from the Qinglong API confirming the creation of the scheduled task, including any identifiers or status messages returned by the service.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Qinglong Panel API.
  • The node uses the Qinglong API endpoints under /open/crons for managing scheduled tasks.
  • Proper configuration of the API authentication token is necessary in n8n credentials settings.
  • Network access to the Qinglong API endpoint is required.

Troubleshooting

  • Common issues:

    • Invalid or missing API authentication token will cause authorization errors.
    • Malformed JSON in the "请求Body" property may lead to parsing errors or API rejection.
    • Incorrect cron expressions can cause the API to reject the schedule.
    • Missing required fields like command, schedule, or name may result in API errors.

  • Error messages:

    • If the operation is not implemented or recognized, the node throws an error indicating the operation is not supported.
    • API errors from Qinglong are propagated and should be checked for details such as invalid parameters or permission issues.

  • Resolution tips:

    • Verify the API key credential is correctly set up and valid.
    • Validate the JSON structure and required fields before execution.
    • Use a cron expression validator to ensure correctness.
    • Check network connectivity to the Qinglong API.

Links and References

Discussion