青龙面板[Qinglong]

Overview

This node integrates with the Qinglong panel API to manage various resources such as environment variables, crontabs, subscriptions, scripts, dependencies, logs, and system settings. Specifically, for the "环境变量" (Environment Variables) resource and the "批量更新变量名" (Batch Rename Variable Names) operation, it allows users to rename multiple environment variables in bulk by sending a PUT request with the new variable name and the IDs of the variables to be renamed.

Common scenarios where this node is beneficial include:

• Automating the management of environment variables across multiple tasks or scripts.
• Renaming environment variables in bulk to maintain consistency or reflect updated naming conventions.
• Integrating Qinglong environment variable management into larger automation workflows.

Practical example:

• You have several environment variables identified by their IDs and want to rename all of them to a new standardized name. Using this node operation, you provide the list of IDs and the new name in JSON format, and the node performs the batch update via the Qinglong API.

Properties

Example value for 请求Body:

{
  "ids": [123, 456, 789],
  "name": "NEW_VARIABLE_NAME"
}

Output

The node outputs the result of the Qinglong API call in the json field under the property result. This typically contains the response from the API indicating success or failure of the batch rename operation, including any relevant messages or data returned by the server.

No binary data output is produced by this operation.

Dependencies

• Requires an API key credential for authenticating with the Qinglong API.
• The node depends on the Qinglong API being accessible and properly configured.
• No additional external services are required beyond the Qinglong API.

Troubleshooting

• Common issues:

  • Invalid or missing API credentials will cause authentication failures.
  • Providing incorrect or empty ids array or invalid name in the request body may lead to API errors.
  • 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 returned from Qinglong will be passed through; check the message for details such as invalid parameters or permission issues.

• Resolution tips:

  • Verify that the API key credential is correctly set up in n8n.
  • Ensure the ids array contains valid environment variable IDs.
  • Confirm the new variable name is a valid string and meets any naming requirements.
  • Check network connectivity and Qinglong API availability.

Links and References

• Qinglong API documentation: https://qinglong.online/api/
• Qinglong project homepage: https://qinglong.online/