Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Customer → Get Many

AI-generated

Overview

This node operation retrieves multiple customer records from the Druva MSP API. It supports filtering customers by their name or account name using various operators (e.g., contains, equals, starts with). Users can choose to return all results or limit the number of results returned. Additionally, it can include customer features in the response if requested. This operation is useful for scenarios where you need to fetch a list of customers for reporting, analysis, or further processing in an automation workflow.

Use Case Examples

  1. Fetch all customers without any filters to get a complete list.
  2. Retrieve up to 50 customers whose names contain a specific substring.
  3. Get customers filtered by account name starting with a certain prefix and include their features in the response.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of customer results to return when 'Return All' is false.
Include Features Whether to include customer features in the response.
Filter by Customer Name Whether to filter results by customer name.
Customer Name Operator Operation to perform when comparing Customer Name values (e.g., contains, equals).
Customer Name Value The value to compare against the customer name.
Filter by Account Name Whether to filter results by account name.
Account Name Operator Operation to perform when comparing Account Name values (e.g., contains, equals).
Account Name Value The value to compare against the account name.
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'.

Output

JSON

  • id - Unique identifier of the customer.
  • customerName - Name of the customer.
  • accountName - Account name associated with the customer.
  • features - Optional features included in the customer response if requested.

Dependencies

  • Druva MSP API with API key credential

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access customer data.
  • If filtering by customer or account name, verify that the operator and value are correctly set to avoid empty results.
  • When 'Return All' is false, ensure the 'Limit' value is within the allowed range (1 to 100).
  • If the node throws an error about an unimplemented resource, verify that the resource parameter is set to 'Customer'.

Discussion