Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The node interacts with the Druva MSP API to manage and monitor tasks among other resources. Specifically, for the Task resource with the Wait for Completion operation, it allows users to wait until a specified task completes before proceeding. This is useful in automation workflows where subsequent steps depend on the successful completion of asynchronous tasks initiated earlier.

Typical use cases include:

  • Waiting for backup or restore jobs to finish before triggering notifications or further processing.
  • Pausing workflow execution until a long-running maintenance task completes.
  • Synchronizing dependent operations that require task completion confirmation.

Properties

Name Meaning
Task ID The unique identifier of the task to wait for completion.
Maximum Wait Time Maximum time (in seconds) to wait for the task to complete. Default is 300 seconds (5 minutes).
Poll Interval Interval (in seconds) between polling attempts to check the task status. Default is 5 seconds.

Output

The node outputs JSON data representing the final state or details of the waited-for task once it completes or the maximum wait time is reached. The output structure typically includes task metadata such as status, result, timestamps, and any relevant response from the Druva MSP API about the task.

If the node supports binary data output (not explicitly shown in the provided code), it would represent associated files or artifacts related to the task, but this is not indicated here.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
  • Network access to https://apis.druva.com.
  • The node depends on internal helper functions to perform API requests and handle pagination.
  • No additional external services are required beyond the Druva MSP API.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication failures.
    • Providing an incorrect or non-existent Task ID will result in errors or indefinite waiting.
    • Setting too short a Maximum Wait Time may cause premature timeout before task completion.
    • Network connectivity issues can interrupt polling and cause errors.

  • Error messages:

    • Errors related to "task not found" indicate the Task ID does not exist or is inaccessible.
    • Timeout errors occur if the task does not complete within the specified Maximum Wait Time.
    • API rate limiting or permission errors may arise if the API key lacks necessary scopes.

  • Resolutions:

    • Verify and update API credentials.
    • Confirm the Task ID is correct and accessible.
    • Adjust Maximum Wait Time and Poll Interval according to expected task duration.
    • Ensure network connectivity and API permissions.

Links and References

Discussion