青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Overview

This node integrates with the Qinglong Panel API to manage various resources such as crontabs, subscriptions, environment variables, configurations, scripts, dependencies, logs, and system settings. Specifically, for the "订阅管理" (Subscription Management) resource and the "启用订阅" (Enable Subscription) operation, it enables one or more selected subscriptions by sending a PUT request to the Qinglong API endpoint responsible for enabling subscriptions.

This node is beneficial in automation workflows where you want to programmatically control subscription states within Qinglong, such as enabling scheduled tasks or services that are managed as subscriptions. For example, you might use this node to enable specific subscriptions after maintenance windows or based on external triggers.

Properties

Name Meaning
订阅列表【可多选】 A multi-select list of subscriptions to enable. The user can select one or multiple subscriptions from available options loaded dynamically from Qinglong.

Output

The node outputs the JSON response from the Qinglong API call under the result field of the first input item's JSON data. This typically contains the API's confirmation or status message about the enable operation performed on the selected subscriptions.

No binary data output is produced by this node.

Example output structure:

{
  "result": {
    // API response confirming enabled subscriptions
  }
}

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests against the Qinglong Panel API.
  • The node depends on Qinglong's REST API being accessible and properly configured.
  • The node uses internal helper functions to obtain authentication tokens and make HTTP requests to Qinglong endpoints.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Selecting subscription IDs that do not exist or have been deleted may result in errors.
    • Network connectivity issues to the Qinglong API server will prevent successful execution.
  • Error messages:

    • If the operation is not implemented or recognized, the node throws an error indicating the operation is not yet supported.
    • API errors returned from Qinglong will be surfaced as node errors; check the API response for details.
  • Resolution tips:

    • Verify that the API key credential is correctly set up and has sufficient permissions.
    • Ensure the subscription IDs selected are valid and currently exist in Qinglong.
    • Confirm network access to the Qinglong API endpoint.
    • Review the exact error message for clues and consult Qinglong API documentation if needed.

Links and References

Discussion