青龙面板[Qinglong] icon

青龙面板[Qinglong]

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

Actions64

Overview

This node integrates with the Qinglong Panel API to manage scheduled tasks and related resources. Specifically, for the "定时任务" (Scheduled Task) resource and the "移动视图位置" (Move View Position) operation, it allows users to reorder views within the Qinglong crontab interface by specifying the original position, target position, and view ID.

Common scenarios include:

  • Automating the rearrangement of task views in Qinglong to prioritize or organize scheduled jobs.
  • Integrating with workflows that dynamically adjust the UI layout of scheduled tasks based on external triggers or conditions.

Practical example:

  • A user wants to move a specific view from position 3 to position 1 in their Qinglong dashboard automatically after certain events, improving visibility of critical tasks.

Properties

Name Meaning
请求Body JSON object containing:
- fromIndex: Original position index (number)
- toIndex: Target position index (number)
- id: The ID of the view to move (number)

Example JSON structure for the property:

{
  "fromIndex": "Original position: number",
  "toIndex": "Target position: number",
  "id": "View ID: number"
}

Output

The node outputs a JSON object under the field result which contains the response from the Qinglong API after attempting to move the view position. This typically includes success status or error details returned by the API.

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 authentication tokens and make HTTP requests to Qinglong's REST endpoints.
  • The base URL and API version are implicitly handled by the node's internal request methods.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid indices or view IDs may result in API errors or no changes.
    • Network connectivity problems 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 propagated and should be checked for details such as invalid parameters or permission issues.

  • Resolution tips:

    • Verify the API key and permissions.
    • Ensure the fromIndex, toIndex, and id values are correct and correspond to existing views.
    • Check network access to the Qinglong API endpoint.

Links and References

Discussion