青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the Qinglong Panel API to manage scheduled tasks (crontabs) and related resources. Specifically, for the "定时任务" (Scheduled Task) resource and the "删除标签" (Delete Tag) operation, it allows users to remove tags from one or more scheduled tasks by sending a DELETE request to the Qinglong API.

Common scenarios where this node is useful include:

  • Automating the cleanup or reorganization of task tags in Qinglong.
  • Removing obsolete or incorrect tags from multiple scheduled tasks in bulk.
  • Managing task metadata programmatically as part of larger automation workflows.

For example, you might use this node to remove specific labels from a batch of scheduled tasks identified by their IDs, helping maintain an organized task environment.

Properties

Name Meaning
请求Body JSON object containing:
- ids: An array of task IDs (number[]) to identify which scheduled tasks to modify.
- labels: An array of tag strings (string[]) to be removed from the specified tasks.

The property expects a JSON input specifying the task IDs and the labels to delete.

Output

The node outputs the JSON response returned by the Qinglong API after attempting to remove the specified tags from the scheduled tasks. This typically includes information about the success or failure of the operation.

The output structure is:

{
  "result": { /* API response data */ }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Qinglong Panel API.
  • The node uses the Qinglong API endpoint /open/crons/labels with the HTTP DELETE method to perform the tag removal.
  • Proper configuration of the Qinglong API credentials within n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing task IDs or labels in the request body may cause the API to reject the request.
    • Authentication failures if the API key credential is not set up correctly.
    • Network connectivity issues preventing access to the Qinglong API.

  • Error messages:

    • If the operation is not implemented or recognized, the node throws an error indicating the operation is not supported.
    • API errors returned from Qinglong will be passed through; these often include HTTP status codes and descriptive messages.

  • Resolutions:

    • Ensure the ids and labels arrays are correctly formatted and contain valid values.
    • Verify that the API key credential is properly configured and has sufficient permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion