Druva MSP icon

Druva MSP

Interact with the Druva MSP API

Actions79

Admin → Get Many

AI-generated

Overview

This node operation retrieves multiple administrator records from the Druva MSP API. It supports filtering administrators by specific IDs, email addresses, or roles, and allows limiting the number of results or returning all available records. This operation is useful for scenarios where you need to manage or analyze administrator data in bulk, such as auditing admin accounts, generating reports, or syncing admin information with other systems.

Use Case Examples

  1. Retrieve all administrators without filters to get a complete list of admins.
  2. Filter administrators by specific admin IDs to get details only for selected admins.
  3. Filter administrators by email address to find a particular admin.
  4. Filter administrators by role to get all admins assigned to certain roles.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit.
Limit Maximum number of administrator results to return when 'Return All' is false.
Filter by Admin IDs Whether to filter administrators by specific IDs.
Admin IDs IDs of the administrators to retrieve when filtering by IDs is enabled.
Filter by Email Whether to filter administrators by email address.
Email Email address to filter administrators by when filtering by email is enabled.
Filter by Role Whether to filter administrators by their role.
Role Roles to filter administrators by when filtering by role is enabled.

Output

JSON

  • id - Unique identifier of the administrator.
  • firstName - First name of the administrator.
  • lastName - Last name of the administrator.
  • email - Email address of the administrator.
  • role - Role(s) assigned to the administrator.
  • status - Status of the administrator account.

Dependencies

  • Druva MSP API with an API key credential

Troubleshooting

  • Ensure the API credentials are correctly configured and have sufficient permissions to access administrator data.
  • If filtering by IDs, email, or role, verify that the filter values are valid and exist in the system.
  • If the node returns an error about the resource not being implemented, confirm that the 'Admin' resource and 'Get Many' operation are supported in the current node version.
  • Network or API rate limiting issues may cause failures; check connectivity and API usage limits.

Discussion