青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

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 "禁用订阅" (Disable Subscription) operation, it allows users to disable one or more subscriptions by their IDs.

Common scenarios include automating subscription lifecycle management in QingLong, such as enabling, disabling, running, or stopping subscriptions programmatically within an n8n workflow. For example, a user might disable certain subscriptions during maintenance windows or based on external triggers.

Properties

Name Meaning
订阅列表【可多选】 List of subscriptions to operate on; multiple selections allowed. The options are dynamically loaded from existing subscriptions in QingLong.

Output

The node outputs the JSON response from the QingLong API corresponding to the requested operation. For the "禁用订阅" operation, this typically includes the result of the disable request, which may be a success confirmation or details about the affected subscriptions.

The output structure is:

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

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the QingLong API.
  • The node uses internal helper functions to obtain an authentication token and make HTTP requests to QingLong's REST API endpoints.
  • The QingLong API base URL and credentials must be configured properly in n8n.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Providing invalid subscription IDs or empty selection may result in errors or no action.
    • Network connectivity issues can prevent API calls from succeeding.

  • 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 by QingLong are propagated and should be checked for details like permission issues or invalid parameters.

  • Resolution tips:

    • Verify that the API key credential is valid and has sufficient permissions.
    • Ensure subscription IDs exist and are correctly selected.
    • Check network access to the QingLong API endpoint.

Links and References

Discussion