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 perform various operations on different resources, including tasks. Specifically, for the Task resource and the Get operation, it retrieves detailed information about a specific task identified by its unique Task ID. This is useful in scenarios where users need to fetch the current status, metadata, or other details of a particular task managed within the Druva MSP environment.

Practical examples include:

  • Retrieving the status and progress of a backup or restore task.
  • Fetching task details to display in dashboards or reports.
  • Automating workflows that depend on task completion or attributes.

Properties

Name Meaning
Task ID The unique identifier of the task to retrieve details for. This must be provided as a string.

Output

The node outputs JSON data representing the detailed information of the requested task. The structure typically includes fields such as task identifiers, status, timestamps, and any relevant metadata returned by the Druva MSP API for that task.

If the node supports binary data output (not explicitly shown in the provided code), it would represent associated files or attachments 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.
  • The base URL for API requests is https://apis.druva.com.
  • The node depends on internal helper functions to make authenticated API calls and handle pagination when fetching data.

Troubleshooting

  • Common issues:

    • Providing an invalid or non-existent Task ID will likely result in an error from the API indicating the task was not found.
    • Network connectivity problems or incorrect API credentials can cause authentication failures or request errors.
    • If the API rate limits are exceeded, requests may fail temporarily.

  • Error messages:

    • Errors thrown during execution will include the message from the API or internal processing errors.
    • When "continue on fail" is enabled, errors for individual items will be returned as JSON objects with an error field describing the issue.

  • Resolutions:

    • Verify the Task ID is correct and exists in the Druva MSP system.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Check network connectivity and retry after some time if rate-limited.

Links and References

Discussion