Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Overview

This node interacts with the Druva MSP API to retrieve multiple customer records based on specified filters and limits. It is useful for scenarios where you need to fetch a list of customers, optionally filtered by customer or account names, such as generating reports, syncing customer data, or performing bulk operations on selected customers.

For example, you can use this node to:

  • Retrieve all customers whose names contain a specific substring.
  • Limit the number of returned customers to avoid processing large datasets.
  • Filter customers by their associated account names using various matching operators.

Properties

Name Meaning
Return All Whether to return all matching customer results or only up to a specified limit.
Limit Maximum number of customer results to return (used only if "Return All" is false).
Filter by Customer Name Enable filtering of customers by their name.
Customer Name Operator The comparison operation to apply when filtering by customer name. Options: Contains, Not Contains, Equals, Not Equals, Starts With, Ends With.
Customer Name Value The string value to compare against the customer name when filtering.
Filter by Account Name Enable filtering of customers by their account name.
Account Name Operator The comparison operation to apply when filtering by account name. Same options as Customer Name Operator.
Account Name Value The string value to compare against the account name when filtering.

Output

The node outputs an array of customer objects in the json field. Each object represents a customer record retrieved from the Druva MSP API. The exact structure depends on the API response but typically includes fields like customer ID, customer name, account name, and other relevant metadata.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
  • The node uses the base URL https://apis.druva.com for API requests.
  • Pagination handling is implemented internally to support returning all results when requested.

Troubleshooting

  • Common issues:

    • API authentication errors due to missing or invalid API credentials.
    • Network connectivity problems preventing access to the Druva MSP API.
    • Filtering parameters that do not match any customers, resulting in empty output.
    • Exceeding API rate limits if requesting too many records without proper pagination.
  • Error messages:

    • Errors related to fetching customers will include messages indicating the failure reason, e.g., "Error fetching customers: [message]".
    • If the resource or operation is not implemented, the node throws an error stating the unsupported resource.
  • Resolutions:

    • Verify API credentials are correctly set up and have necessary permissions.
    • Check network connectivity and proxy settings if applicable.
    • Adjust filter values or disable filters to broaden search criteria.
    • Use the "Return All" option carefully to avoid large data loads; use "Limit" to restrict result size.

Links and References

Discussion