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 Provisioning Report
AI-generatedOverview
This node interacts with the Druva MSP API to retrieve user provisioning 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 provisioning 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 user provisioning activities for the previous month filtered by specific customers and provisioning statuses to analyze provisioning success rates.
- A user needs to fetch all user provisioning records without date filtering to audit provisioning activities across all time.
Properties
| Name | Meaning |
|---|---|
| Date Selection Method | Choose whether to use specific dates, relative date ranges, or include all dates (no date filter). |
| Start Date | Start date for the report period, required if using specific dates. |
| End Date | End date for the report period, required if using specific dates. |
| Date Range | Select a predefined relative date range for the report, used if relative date range method 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. |
| Filter by Provisioning Status | Whether to filter results by provisioning status. |
| Provisioning Status | Provisioning status values to filter by, such as Successful, Failed, In Progress, or Pending. |
| 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 provisioning report data as JSON objects.
Dependencies
- Druva MSP API with an API key credential
Troubleshooting
- Ensure the API credentials are correctly configured and have sufficient permissions to access the Report - Endpoint resource.
- If filtering by customers or provisioning status, verify that the provided IDs and status values are valid and exist in the system.
- If the node returns no data, check the date filters and ensure the selected date range contains data.
- Common error messages may include authentication errors, invalid parameter errors, or API rate limit errors. Verify credentials, parameter values, and retry after some time if rate limited.