Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Customer → Get

AI-generated

Overview

This node interacts with the Druva MSP API to retrieve detailed information about a specific customer. It is useful in scenarios where you need to fetch customer data, optionally including their features, for further processing or integration within an automation workflow. For example, you might use this node to get customer details before generating reports or managing customer-related tasks.

Use Case Examples

  1. Retrieve a customer's details by their unique ID to display or process in a CRM system.
  2. Fetch customer information including features to analyze service usage or entitlements.

Properties

Name Meaning
Customer ID The unique ID of the customer to perform the operation on. This is a required field and is selected from a dynamically loaded list of customers.
Include Features A boolean flag indicating whether to include customer features in the response. Defaults to false.
Wrap Output Items When enabled, wraps all output items into a single item containing an array to prevent the next node from executing multiple times.
Wrapper Property Name The property name to use for the wrapped array of items in the output. Default is 'items'. This is only shown if 'Wrap Output Items' is enabled.

Output

JSON

  • json - The main output object containing customer data retrieved from the Druva MSP API.

Dependencies

  • Druva MSP API with an API key credential

Troubleshooting

  • If the node fails to retrieve customers, ensure the API credentials are correct and have sufficient permissions.
  • Errors related to missing or invalid Customer ID indicate that the selected customer does not exist or the ID is incorrect.
  • If the 'Include Features' option is enabled but features are not returned, verify that the customer has features assigned in the Druva MSP system.
  • When 'Wrap Output Items' is enabled, downstream nodes will receive a single item with an array; ensure they can handle this structure to avoid processing errors.

Discussion