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 Workload Report
AI-generatedOverview
This node interacts with the Druva MSP API to retrieve Google User Workload Reports under the 'Report - Enterprise Workloads' resource. It supports fetching detailed workload data for Google users within an enterprise environment, allowing filtering by date ranges, customers, and other parameters. This is useful for MSPs or administrators who need to monitor and analyze Google Workspace usage and workloads across their enterprise clients.
Use Case Examples
- Fetch all Google User Workload Reports for the previous month to analyze user activity trends.
- Retrieve a limited number of reports filtered by specific customer IDs for targeted analysis.
- Use specific start and end dates to get workload reports for a custom date range.
Properties
| Name | Meaning |
|---|---|
| Return All | Determines whether to return all available results or limit the output to a specified number. |
| Limit | Specifies the maximum number of results to return when 'Return All' is false. |
| Date Selection Method | Selects the method for filtering report data by date: no filter, specific dates, or relative date ranges. |
| Start Date | The inclusive start date for filtering report data when using specific dates. |
| End Date | The inclusive end date for filtering report data when using specific dates. |
| Date Range | Predefined relative date ranges for filtering report data when using relative dates. |
| Filter by Customer(s) | Enables filtering the report results by specific customer IDs. |
| Customer IDs | List of customer IDs to filter the report results by when filtering by customers is enabled. |
| 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 when wrapping is enabled. |
Output
JSON
items- An array containing the list of Google User Workload Report items when output wrapping is enabled.count- The total count of report items included in the wrapped output.
Dependencies
- Requires Druva MSP API access with appropriate credentials.
Troubleshooting
- Ensure the API credentials are correctly configured and have permissions to access enterprise workload reports.
- If filtering by customers, verify that the customer IDs are valid and accessible.
- When using date filters, ensure the dates are in the correct format and logical (start date before end date).
- If the node returns an error about the resource not being implemented, verify the resource and operation parameters are correctly set.