青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the Qinglong Panel API, a platform for managing scheduled tasks and related resources. Specifically, the "配置文件" (Configuration File) resource with the "获取文件详情" (Get File Details) operation allows users to retrieve detailed information about a specific configuration file stored in Qinglong.

Common scenarios where this node is beneficial include:

  • Automating retrieval of configuration file details for monitoring or auditing.
  • Integrating configuration data into workflows for dynamic task adjustments.
  • Fetching config metadata before performing updates or backups.

For example, a user might use this node to fetch the details of a particular config file by its ID, then use that data downstream to decide whether to update or notify about changes.

Properties

Name Meaning
配置文件 The configuration file to get details for. This is selected from a list of available configs.

The property "配置文件" corresponds to configId internally and requires selecting a config resource locator, typically from a searchable list.

Output

The node outputs JSON data under the .json.result field containing the detailed information of the requested configuration file as returned by the Qinglong API endpoint /open/configs/detail. The structure depends on the API response but generally includes metadata and content details of the config file.

No binary data output is indicated for this operation.

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 endpoints.
  • No additional external dependencies beyond the Qinglong API and n8n's credential system.

Troubleshooting

  • Common issues:

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

  • Error messages:

    • If the operation is not implemented or unsupported, the node throws an error indicating the operation is not yet implemented.
    • API errors from Qinglong are wrapped and surfaced as node errors; check the message for details such as "config_detail operation not implemented" or HTTP error codes.

  • Resolutions:

    • Ensure the API key credential is correctly configured and has necessary permissions.
    • Verify the config ID exists and is correctly selected.
    • Check network access to the Qinglong API endpoint.

Links and References

Discussion