青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the QingLong Panel API to manage various resources such as scheduled tasks (crontabs), subscriptions, environment variables, configurations, scripts, dependencies, logs, and system settings. Specifically, for the "订阅管理" (Subscription Management) resource and the "停止订阅" (Stop Subscription) operation, it allows users to stop one or multiple subscriptions by their IDs.

Common scenarios include:

  • Temporarily halting subscription-based tasks without deleting them.
  • Managing active subscriptions programmatically within an automation workflow.
  • Controlling subscription execution states in bulk.

For example, a user can select multiple subscription IDs and stop all of them at once, which is useful when maintenance or troubleshooting is needed.

Properties

Name Meaning
订阅列表【可多选】 A multi-select list of subscription IDs to specify which subscriptions to stop.

The property "订阅列表【可多选】" lets the user pick one or more subscriptions from available subscriptions loaded dynamically via the API.

Output

The node outputs the result of the API call in the json field under the key result. This typically contains the response data from the QingLong API indicating success or failure of the stop operation on the specified subscriptions.

No binary data output is involved.

Example output JSON structure:

{
  "result": {
    // API response details about stopped subscriptions
  }
}

Dependencies

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

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Specifying subscription IDs that do not exist or are already stopped may lead to errors or no effect.
    • Network connectivity problems can prevent successful API calls.

  • 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 are wrapped and surfaced as node errors.

  • Resolutions:

    • Verify API credentials and permissions.
    • Confirm subscription IDs are correct and currently active.
    • Check network access to the QingLong API endpoint.

Links and References

Discussion