Actions79
- Admin Actions
- Alert Summary Actions
- Backup Health Summary Actions
- Consumption Billing Analyzer Actions
- Customer Actions
- Event Actions
- Report - Cyber Resilience Actions
- Report - Endpoint Actions
- Report - Enterprise Workloads Actions
- Get Alert History Report
- Get Backup Activity Report
- Get DR Failback Activity Report
- Get DR Failover Activity Report
- Get DR Replication Activity Report
- Get Resource Status Report
- Get Storage Consumption by BackupSets Report
- Get Google Alerts Report
- Get Google License Usage Report
- Get Google Preserved Users Datasources Report
- Get Google Shared Drive Backup Activity Report
- Get Google Shared Drive Restore Activity Report
- Get Google Storage Consumption Report
- Get Google User Count and Status Report
- Get Google User Last Backup Status Report
- Get Google User Provisioning Report
- Get Google User Restore Activity Report
- Get Google User Workload Report
- Get M365 Alerts Report
- Get M365 Groups Backup Activity Report
- Get M365 Groups Discovery Report
- Get M365 License Usage Report
- Get M365 Preserved Users Datasources Report
- Get M365 Public Folder Backup Activity Report
- Get M365 SharePoint Backup Activity Report
- Get M365 SharePoint Site Discovery Report
- Get M365 Storage Consumption Report
- Get M365 Teams Backup Activity Report
- Get M365 Teams Discovery Report
- Get M365 User Count and Status Report
- Get M365 User Last Backup Status Report
- Get M365 User Provisioning Report
- Get M365 User Restore Activity Report
- Get M365 User Workload Report
- Report - Usage Actions
- Service Plan Actions
- Storage Region Actions
- Task Actions
- Tenant Actions
- Tenant Config - Enterprise Workloads Actions
- Tenant Config - inSync Actions
Report - Endpoint → Get User Report
AI-generatedOverview
The node interacts with the Druva MSP API to retrieve user reports from the Report - Endpoint resource. It supports filtering the report data by date ranges (all dates, specific dates, or relative date ranges), customer IDs, and user status. The node can return all results or limit the number of results, and it offers an option to wrap all output items into a single item containing an array to prevent multiple executions downstream.
Use Case Examples
- A user wants to generate a report of endpoint users for the previous month filtered by specific customers.
- A user needs to get a user report for a custom date range and filter by active user status.
Properties
| Name | Meaning |
|---|---|
| Date Selection Method | Choose whether to use specific dates, relative date ranges, or include all dates (no date filter). Options: All Dates, Specific Dates, Relative Date Range. |
| Start Date | Start date for the report period, required if 'Specific Dates' is selected. |
| End Date | End date for the report period, required if 'Specific Dates' is selected. |
| Date Range | Select a predefined relative date range for the report, required if 'Relative Date Range' is selected. |
| Filter by Customers | Whether to filter results by specific customer IDs. |
| Customer IDs | List of customer IDs to include in the report, required if filtering by customers is enabled. |
| Filter by User Status | Whether to filter results by user status. |
| User Status | User status values to filter by, required if filtering by user status is enabled. Options: Active, Deactivated, Preserved. |
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return if not returning all. |
| Wrap Output Items | When enabled, wraps all output items into a single item containing an array to prevent the next node from executing multiple times. |
| Wrapper Property Name | The property name to use for the wrapped array of items in the output. Default is 'items'. |
Output
JSON
json- The main output containing the user report data as JSON objects.
Dependencies
- Druva MSP API
- an API key credential for authentication
Troubleshooting
- Ensure the API credentials are correctly configured to avoid authentication errors.
- If filtering by customers or user status, ensure the IDs and status values are valid and exist in the system.
- If the node returns no data, verify the date range and filters are correctly set to match available data.
- Errors related to resource or operation not implemented indicate a misconfiguration of the resource or operation parameters.