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 - Enterprise Workloads → Get Google User Last Backup Status Report
AI-generatedOverview
This node operation fetches the Google User Last Backup Status Report from the Druva MSP API under the 'Report - Enterprise Workloads' resource. It is useful for administrators or IT professionals who need to monitor backup statuses of Google users within an enterprise environment. The node supports filtering by date ranges (specific or relative), limiting the number of results, and filtering by specific customers. It can return all results or a limited subset based on user configuration. The output can be wrapped into a single item to simplify downstream processing.
Use Case Examples
- An IT admin wants to generate a report showing the last backup status of all Google users for the previous month to ensure compliance with backup policies.
- A support team filters the report to only include specific customers to troubleshoot backup issues for those clients.
- A manager requests a limited number of recent backup status entries for quick review.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit. |
| Limit | Maximum number of results to return when 'Return All' is false. |
| Date Selection Method | Choose whether to use specific dates, relative date ranges, or include all dates (no date filter). |
| Start Date | Start date for filtering report data (inclusive), used when 'Specific Dates' is selected. |
| End Date | End date for filtering report data (inclusive), used when 'Specific Dates' is selected. |
| Date Range | Predefined relative date range for filtering report data, used when 'Relative Date Range' is selected. |
| Filter by Customer(s) | Whether to filter results by specific customers. |
| Customer IDs | IDs of the customers to filter by, used when 'Filter by Customer(s)' is true. |
| 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
items- Array of report items when output is wrapped.count- Count of report items when output is wrapped.
Dependencies
- Druva MSP API with appropriate API key credentials
Troubleshooting
- Ensure API credentials are correctly configured to avoid authentication errors.
- If the report returns no data, verify the date filters and customer filters are set correctly.
- When 'Return All' is false, the limit must be between 1 and 100; setting outside this range may cause errors.
- If the node fails, enabling 'Continue On Fail' can help to handle errors gracefully and continue processing other items.