Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

This node integrates with the Druva MSP API to perform various operations on different resources, including Service Plans. Specifically, the "Get" operation for the Service Plan resource retrieves detailed information about a single service plan identified by its unique ID. This is useful in scenarios where you need to fetch configuration details, features, or status of a particular service plan within your managed service provider environment.

Practical examples include:

  • Retrieving a service plan's details to display or process them in workflows.
  • Validating if a service plan exists before assigning it to a customer or tenant.
  • Automating reporting or auditing tasks that require service plan metadata.

Properties

Name Meaning
Service Plan ID Unique identifier of the service plan to retrieve. This is a required string input.

Output

The node outputs JSON data representing the service plan details fetched from the Druva MSP API. The structure typically includes fields such as the service plan's ID, name, features, edition, status, and other metadata provided by the API.

If the node supports binary data output (not indicated here), it would represent associated files or attachments related to the service plan, but this is not applicable based on the provided code.

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 handle API requests and pagination.
  • No additional external services are explicitly required beyond the Druva MSP API.

Troubleshooting

  • Common issues:

    • Invalid or missing Service Plan ID will cause the API request to fail.
    • Network connectivity problems or incorrect API credentials can prevent successful API calls.
    • If the specified service plan does not exist, the API may return an error or empty response.

  • Error messages:

    • Errors thrown during execution will include the message from the API or internal processing errors.
    • If the resource or operation is not implemented, the node throws an explicit error indicating so.

  • Resolutions:

    • Verify the Service Plan 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 API endpoint accessibility.
    • Use the "Continue On Fail" option in the node settings to handle errors gracefully in workflows.

Links and References

Discussion