Actions64
- 定时任务 Actions
- 订阅管理 Actions
- 环境变量 Actions
- 配置文件 Actions
- 脚本管理 Actions
- 依赖管理 Actions
- 日志管理 Actions
- 系统设置 Actions
Overview
This node integrates with the Qinglong panel API to manage various resources such as scripts, crontabs, subscriptions, environment variables, configurations, dependencies, logs, and system settings. Specifically, for the "脚本管理" (Script Management) resource and the "获取脚本详情" (Get Script Details) operation, it fetches detailed information about a specific script file located at a given path.
Common scenarios where this node is useful include:
- Retrieving the content or metadata of a script stored in the Qinglong panel.
- Automating script management workflows by programmatically accessing script details.
- Integrating Qinglong script data into larger automation pipelines within n8n.
Practical example:
- You want to get the details of a script named
backup.shlocated in/scripts/daily/to verify its content before triggering an update or execution.
Properties
| Name | Meaning |
|---|---|
| 脚本路径 | The directory path where the script is located. Example: /scripts/daily/ |
| 文件名 | The filename of the script to retrieve details for. Example: backup.sh |
Output
The node outputs JSON data under the .json.result field containing the detailed information of the requested script. This typically includes script metadata and content as returned by the Qinglong API's /open/scripts/detail endpoint.
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's REST API endpoints.
- Proper configuration of the Qinglong API credentials in n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect script path or filename parameters may result in "not found" errors from the API.
- 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 are wrapped and thrown as node errors with descriptive messages.
Resolutions:
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Double-check the script path and filename inputs for accuracy.
- Ensure the Qinglong panel server is reachable from the n8n instance.
Links and References
- Qinglong Panel API documentation: https://qinglong.online/api/
- n8n Documentation on creating custom nodes: https://docs.n8n.io/integrations/creating-nodes/