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 related to managed service provider resources. Specifically, for the Customer resource and the Get Token operation, it retrieves an authentication token or similar credential associated with a specified customer. This is useful in scenarios where you need to programmatically access or manage customer-specific data or services within the Druva MSP platform.

Practical examples include:

  • Automating workflows that require customer-specific tokens to authenticate further API calls.
  • Integrating Druva MSP customer data into other systems by first obtaining the necessary token.
  • Managing multiple customers by dynamically retrieving their tokens during batch processing.

Properties

Name Meaning
Customer ID The unique identifier of the customer for whom the token will be retrieved. Options are dynamically loaded from the list of available customers.

Output

The node outputs JSON data containing the result of the "Get Token" operation for the specified customer. The structure typically includes fields representing the token and possibly metadata about the token or customer. The exact JSON structure depends on the Druva MSP API response for this operation.

If the node supports binary data output (not explicitly shown here), it would represent any binary content returned by the API, such as certificates or encoded files related to the token.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key or authentication token configured in n8n credentials.
  • Uses the Druva MSP base URL: https://apis.druva.com.
  • Relies on internal helper functions to make authenticated API requests and handle pagination when loading options.
  • The "Customer ID" property options are dynamically loaded by querying the /msp/v2/customers endpoint.

Troubleshooting

  • Error fetching customers: If the dropdown for Customer ID fails to populate, check network connectivity and API credentials.
  • Invalid or missing Customer ID: Ensure the selected Customer ID exists and is valid; otherwise, the API call to get the token may fail.
  • API rate limits or permission errors: Verify that the API key has sufficient permissions to access customer tokens.
  • Unexpected API errors: The node captures and logs errors; enabling debug logging can help identify issues.
  • Continue on Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error details in the output JSON.

Links and References

Discussion