青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the Qinglong Panel API to manage and interact with various resources such as crontabs, subscriptions, environment variables, configurations, scripts, dependencies, logs, and system settings. Specifically, for the resource 订阅管理 (Subscription Management) and operation 获取订阅日志列表 (Get Subscription Log List), the node fetches the list of execution logs related to a specified subscription.

This functionality is useful when you want to monitor or audit the execution history of a particular subscription in Qinglong. For example, you might use this node to retrieve logs to analyze failures, check execution times, or verify that scheduled tasks ran as expected.

Properties

Name Meaning
Subscription The subscription to filter the execution logs by. You can select from a list of existing subscriptions or provide a subscription ID manually.

The "Subscription" property supports two modes:

  • From List: Select a subscription from a searchable dropdown list.
  • ID: Enter a valid subscription ID string manually (must match regex [0-9a-zA-Z]{1,}).

Output

The node outputs JSON data under the json field of the first input item. The key result contains the response from the Qinglong API endpoint /open/subscriptions/{subscriptionId}/logs, which is an array or object representing the logs associated with the specified subscription.

The structure of each log entry depends on the Qinglong API but typically includes details such as timestamps, status, messages, and other metadata about each execution instance.

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential configured in n8n to access the Qinglong Panel API.
  • The node calls the Qinglong API endpoint /open/subscriptions/{subscriptionId}/logs using HTTP GET.
  • Proper network connectivity to the Qinglong API server is necessary.

Troubleshooting

  • Invalid Subscription ID: If the subscription ID is invalid or not found, the API may return an error. Ensure the subscription exists and the ID format is correct.
  • Authentication Errors: Missing or incorrect API credentials will cause authentication failures. Verify that the API key/token is correctly set up in n8n credentials.
  • API Endpoint Not Implemented: If the operation is not supported by the current version of the Qinglong API, the node throws an error indicating the operation is not implemented.
  • Network Issues: Connectivity problems to the Qinglong API server will result in request failures. Check your network and firewall settings.

Links and References

Discussion