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 various reports and data related to endpoint management, including user rollout reports. Specifically, the "Get User Rollout Report" operation under the "Report - Endpoint" resource fetches detailed information about user rollout statuses within a specified date range and optionally filtered by customers or rollout status.

Common scenarios for this node include:

  • Monitoring the progress of software or policy rollouts across multiple users or endpoints.
  • Generating reports for compliance or auditing purposes on rollout completion.
  • Filtering rollout data by specific customers or statuses to focus on particular segments.

Practical example:

  • A managed service provider wants to generate a report showing all users who have completed a security patch rollout in the last month for selected customers. They can use this node to specify the date range as "Last 30 Days," filter by those customers, and only include rollout statuses marked as "Completed."

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 using Specific Dates).
End Date The end date for the report period (required if using Specific Dates).
Date Range Select a predefined relative date range for the report when using Relative Date Range method. 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 indicate whether to filter the report results by specific customer IDs.
Customer IDs List of customer IDs to include in the report (required if filtering by customers).
Filter by Rollout Status Boolean flag to indicate whether to filter results by rollout status (only shown for the Get User Rollout operation).
Rollout Status List of rollout status values to filter by. Options: Completed, In Progress, Not Started, Failed.
Return All Whether to return all results or limit the number of results returned.
Limit Maximum number of results to return if not returning all. Minimum value is 1.

Output

The node outputs JSON data representing the user rollout report entries matching the specified filters. Each item in the output array corresponds to a rollout record, typically including fields such as user identifiers, rollout status, timestamps, and associated customer information.

If binary data were involved (not indicated here), it would represent files or attachments related to the report, but this operation focuses on JSON data.

Dependencies

  • Requires an active connection to the Druva MSP API via an API key credential configured in n8n.
  • The node uses the Druva MSP API base URL https://apis.druva.com.
  • For loading options like customer IDs, the node makes additional API calls to fetch available customers.
  • Proper permissions on the API key are necessary to access reporting endpoints and customer data.

Troubleshooting

  • Common issues:

    • Invalid or expired API credentials will cause authentication errors.
    • Specifying a date range where the start date is after the end date may result in empty or error responses.
    • Filtering by customers without selecting any customer IDs will likely cause validation errors.
    • Requesting too many records without enabling "Return All" may truncate results unexpectedly.

  • Error messages:

    • "The resource 'reportEndpoint' is not implemented!" indicates a misconfiguration or unsupported resource selection.
    • API errors from Druva MSP (e.g., 401 Unauthorized, 400 Bad Request) should be checked for correct credentials and parameter formatting.
    • Errors during option loading (e.g., fetching customers) will appear as logged errors and may show placeholder error messages in dropdowns.

To resolve these:

  • Verify API credentials and permissions.
  • Ensure date parameters are valid and consistent.
  • When filtering by customers or rollout status, ensure at least one valid option is selected.
  • Use the "Return All" option carefully to avoid large data loads.

Links and References

Discussion