青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the Qinglong Panel API to manage and interact with scheduled tasks (crontabs) and related resources. Specifically, for the "定时任务" (Scheduled Task) resource and the "获取任务日志" (Get Task Log) operation, it fetches execution logs of a specified crontab task by its ID.

Use cases include:

  • Retrieving detailed logs of a particular scheduled task to monitor its execution history.
  • Debugging or auditing scheduled jobs by examining their run logs.
  • Automating log retrieval for further processing or alerting in workflows.

Example: You have a scheduled job running daily backups, and you want to automatically fetch its latest execution logs after each run to verify success or capture errors.

Properties

Name Meaning
Crontab The specific scheduled task (crontab) to filter the execution logs by. This is selected via a resource locator that allows choosing from a list of available crontabs or entering an ID manually.

Output

The node outputs JSON data under the json field of the first input item, with a property named result containing the fetched logs from the Qinglong API.

The structure of result depends on the Qinglong API response for the endpoint /open/crons/{crontabId}/log. Typically, this includes details such as timestamps, execution status, output messages, and error information related to the specified crontab's runs.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Qinglong Panel API.
  • The node uses internal helper functions to obtain an authentication token and make HTTP requests to Qinglong endpoints.
  • No additional external dependencies are required beyond the configured API credentials.

Troubleshooting

  • Common issues:

    • Invalid or missing crontab ID: Ensure the crontab ID provided exists and is correctly formatted.
    • Authentication failures: Verify that the API key credential is valid and has sufficient permissions.
    • Network or API endpoint errors: Check network connectivity and Qinglong API availability.

  • Error messages:

    • If the operation is not implemented or recognized, the node throws an error indicating the operation is not supported.
    • API request errors will be surfaced as node API errors with descriptive messages from the Qinglong API.

  • Resolution tips:

    • Double-check the crontab selection in the node parameters.
    • Confirm API credentials and permissions.
    • Review Qinglong API documentation for any changes or deprecations.

Links and References

Discussion