Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The node interacts with the Druva MSP API to retrieve user reports from the "Report - Endpoint" resource, specifically supporting the "Get User Report" operation. It allows users to generate detailed reports about users within a specified date range and apply filters such as customer IDs and user status. This node is beneficial for MSP administrators or analysts who need to monitor user activity, compliance, or usage patterns over time.

Practical examples include:

  • Generating a report of all active users in specific customers during the last 30 days.
  • Retrieving user reports for a custom date range to analyze trends or audit user statuses.
  • Filtering reports by user status (e.g., only deactivated users) to manage account lifecycle.

Properties

Name Meaning
Date Selection Method Choose whether to use all dates (no filter), specific start and end dates, or a relative date range for the report period. Options: All Dates, Specific Dates, Relative Date Range.
Start Date The start date for the report period (required if "Specific Dates" is selected).
End Date The end date for the report period (required if "Specific Dates" is selected).
Date Range Select a predefined relative date range for the report when "Relative Date Range" is selected. Options include Current Month, Previous Month, Current Quarter, Previous Quarter, Current Year, Previous Year, Last 30/60/90 Days, Last 6/12 Months, Year To Date.
Filter by Customers Boolean flag to enable filtering the report results by specific customer IDs.
Customer IDs List of customer IDs to include in the report (required if filtering by customers is enabled).
Return All Boolean flag indicating whether to return all results or limit the number of returned items.
Limit Maximum number of results to return if "Return All" is false. Minimum value is 1.

Output

The node outputs JSON data representing the user report retrieved from the Druva MSP API. The structure typically includes user details and associated metadata filtered according to the input parameters (date range, customers, user status). The output can be an array of user report objects, each containing fields relevant to user activity and status.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the Druva MSP API.
  • The node depends on the Druva MSP API being accessible at https://apis.druva.com.
  • The node uses internal helper functions to paginate and fetch all items from the API when needed.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid date ranges (e.g., start date after end date) may result in errors or empty responses.
    • Selecting filters without providing required values (e.g., enabling customer filter but not specifying any customer IDs) will likely cause validation errors.
    • Network connectivity issues or API downtime can prevent successful data retrieval.

  • Error Messages:

    • Errors related to fetching customers or other options indicate problems with API requests; ensure credentials and network are correct.
    • If the node throws an error stating the resource is not implemented, verify that the "Resource" parameter is set correctly to "Report - Endpoint".
    • Validation errors for missing required parameters (like start/end dates when using specific dates) should be resolved by providing valid inputs.

Links and References

Discussion