Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

This node interacts with the Druva MSP API to retrieve multiple tenant records, optionally filtered by customer ID, tenant status, or tenant type. It is useful in scenarios where you need to list tenants managed under a Druva MSP account, for example, to audit tenant information, generate reports, or integrate tenant data into other workflows.

Practical examples:

  • Fetch all tenants associated with a specific customer to monitor their backup status.
  • Retrieve tenants filtered by their operational status (e.g., active or inactive) for targeted maintenance.
  • Limit the number of tenants returned to avoid processing large datasets at once.

Properties

Name Meaning
Return All Whether to return all tenant results or only up to a specified limit.
Limit Maximum number of tenant results to return when "Return All" is false.
Filter by Customer Enable filtering tenants by a specific customer ID.
Customer ID The customer ID to filter tenants by (selectable from available customers).
Filter by Tenant Status Enable filtering tenants by their status.
Tenant Status The status of tenants to filter by (selectable from predefined tenant status options).
Filter by Tenant Type Enable filtering tenants by their type.
Tenant Type The type of tenants to filter by (selectable from predefined tenant type options).

Output

The node outputs an array of tenant objects in the json field. Each object represents a tenant and includes details such as tenant ID, tenant name, and other metadata as provided by the Druva MSP API.

If binary data were involved, it would be summarized here, but this operation deals solely with JSON data representing tenant information.

Dependencies

  • Requires an API key credential for authenticating with the Druva MSP API.
  • The node uses the base URL https://apis.druva.com.
  • Pagination handling is implemented internally to fetch all items if requested.
  • The node depends on helper methods to load options dynamically for customers, tenant statuses, and tenant types.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Filtering by customer requires selecting a valid customer ID; otherwise, no tenants may be returned.
    • Setting conflicting filters or invalid filter values might result in empty responses.
    • Exceeding API rate limits could cause temporary errors.

  • Error messages:

    • Errors related to fetching customers or tenants typically include the API error message. Ensure the API key has sufficient permissions.
    • If the resource or operation is not implemented, the node throws an error indicating the unsupported resource.
    • Network or timeout errors should be checked by verifying connectivity and API availability.

Links and References

Discussion