青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the Qinglong Panel API, a platform for managing scheduled tasks, environment variables, scripts, dependencies, and configuration files. It allows users to perform various operations on these resources programmatically within n8n workflows.

Specifically, for the resource "配置文件" (Configuration File), the node supports fetching details of a specified configuration file or retrieving a single configuration file by its ID. This is useful in scenarios where you want to automate the retrieval and processing of configuration files managed in Qinglong, such as syncing config files, auditing changes, or triggering workflows based on config content.

Example use cases:

  • Automatically fetch a specific configuration file before running a deployment script.
  • Retrieve configuration details to validate or log them in an external system.
  • Use configuration data as input parameters for other automation steps.

Properties

Name Meaning
配置文件 (configId) The identifier of the configuration file to retrieve. Can be selected from a list of available configs. Required for operations that fetch specific config details or a single config file.

Output

The node outputs a JSON object under the json.result field containing the response from the Qinglong API for the requested operation. For the "获取指定文件" (get specified file) operation on the "配置文件" resource, this will typically be the detailed information or content of the specified configuration file.

No binary data output is indicated in the code.

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 Qinglong's REST API endpoints.
  • No additional external services are required beyond access to the Qinglong API.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Providing an invalid or non-existent config ID will result in errors or empty responses.
    • Network connectivity issues can prevent successful API calls.

  • Error messages:

    • If an unsupported operation is selected for the "配置文件" resource, the node throws an error indicating the operation is not implemented.
    • Errors from the Qinglong API are propagated and wrapped as node API errors, including descriptive messages.

  • Resolutions:

    • Ensure valid API credentials are configured in n8n.
    • Verify the config ID exists and is accessible.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion