Actions64
- 定时任务 Actions
- 订阅管理 Actions
- 环境变量 Actions
- 配置文件 Actions
- 脚本管理 Actions
- 依赖管理 Actions
- 日志管理 Actions
- 系统设置 Actions
Overview
This node integrates with the QingLong Panel API, a platform for managing scheduled tasks and dependencies. Specifically, the "依赖管理" (Dependency Management) resource with the "获取单个依赖" (Get Single Dependency) operation allows users to retrieve detailed information about a single dependency by its ID and type.
Common scenarios where this node is beneficial include:
- Monitoring or auditing specific dependencies installed in the QingLong environment.
- Fetching metadata or status of a particular dependency before performing updates or removals.
- Integrating dependency details into automated workflows for reporting or conditional logic.
For example, a user might want to get details about a Node.js package dependency to verify its version or installation status before triggering an update process.
Properties
| Name | Meaning |
|---|---|
| 类型 (dependenceType) | The type of dependency to query. Options: nodejs, python3, linux. |
| 依赖 (dependenceId) | The identifier of the specific dependency to retrieve. Can be selected from a list or entered as an ID string. |
Output
The node outputs JSON data under the .json.result field containing the detailed information of the requested dependency. This typically includes all metadata returned by the QingLong API for that dependency, such as name, version, status, and other relevant attributes.
No binary data output is involved in 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 endpoints.
- No additional external services are required beyond access to the QingLong API.
Troubleshooting
- Invalid Dependency ID: If the provided dependency ID does not match any existing dependency, the API will likely return an error. Ensure the ID is correct and corresponds to the selected dependency type.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly configured in n8n.
- Unsupported Operation: If the operation or resource parameters are incorrect or unsupported, the node throws an error indicating the operation is not implemented.
- Network Issues: Connectivity problems with the QingLong API endpoint can cause request failures. Check network access and API availability.
Links and References
- QingLong Panel API Documentation: https://qinglong.online/api/
- QingLong GitHub Repository: https://github.com/whyour/qinglong
- n8n Documentation on Creating Custom Nodes: https://docs.n8n.io/integrations/creating-nodes/