青龙面板[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 "获取任务日志列表" (Get Task Log List) operation, it fetches a list of execution logs for a specified crontab task.

This node is useful when you want to programmatically retrieve historical execution logs of scheduled tasks managed by Qinglong, enabling monitoring, auditing, or triggering workflows based on task outcomes.

Example use cases:

  • Automatically fetching recent execution logs of a scheduled job to analyze success/failure rates.
  • Integrating task logs into dashboards or alerting systems.
  • Archiving logs externally for compliance or backup.

Properties

Name Meaning
Crontab The specific scheduled task (crontab) to filter the execution logs by. This can be selected from a list of available crontabs or provided as an ID string.

Output

The node outputs JSON data under the json field of the first input item, with a property named result containing the response from the Qinglong API endpoint /open/crons/{crontabId}/logs.

The structure of result corresponds to the list of logs for the specified crontab, typically including details such as timestamps, execution status, output messages, and other metadata about each run.

No binary data output is produced by this operation.

Dependencies

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

Troubleshooting

  • Common issues:

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

  • Error messages:

    • If the operation is not implemented or unsupported, the node throws an error indicating the operation is not yet implemented.
    • API errors are wrapped and reported as node API errors with descriptive messages.

  • 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