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 user provisioning, customers, tenants, service plans, tasks, events, admins, and usage statistics. Specifically, for the Report - Endpoint resource and the Get User Provisioning Report operation, it fetches a report on user provisioning activities filtered by date ranges, customer IDs, and provisioning statuses.

Common scenarios where this node is beneficial include:

  • Generating compliance or audit reports on user provisioning activities within an organization.
  • Monitoring provisioning success and failure rates over specific periods.
  • Filtering reports by customers or provisioning status to focus on particular segments or issues.

Practical example:

  • A company wants to review all user provisioning attempts in the last month that failed, to investigate potential problems. They would configure this node to select the "Report - Endpoint" resource, "Get User Provisioning Report" operation, set the date range to "Previous Month," filter by provisioning status "Failed," and optionally filter by specific customers.

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 of the report period (required if "Specific Dates" is selected).
End Date The end date of the report period (required if "Specific Dates" is selected).
Date Range Select a predefined relative date range for the report when "Relative Date Range" is selected. 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 enable filtering the report 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 Provisioning Status Boolean flag to enable filtering the report results by provisioning status.
Provisioning Status List of provisioning status values to filter by (required if filtering by provisioning status is enabled). Options: Successful, Failed, In Progress, Pending.
Return All Boolean flag indicating whether to return all results or limit the number of results returned.
Limit Maximum number of results to return if "Return All" is false. Minimum value is 1.

Output

The node outputs JSON data representing the user provisioning report entries matching the specified filters. Each item in the output array corresponds to a provisioning event or record, including details such as timestamps, customer information, provisioning status, and other relevant metadata.

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

Dependencies

  • Requires an active connection to the Druva MSP API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node uses internal helper functions to paginate through API responses and load options dynamically (e.g., customer lists).
  • No additional external services beyond Druva MSP API are required.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Selecting specific dates without providing both start and end dates will result in validation errors.
    • Filtering by customers requires valid customer IDs; empty or incorrect IDs may yield empty results.
    • Exceeding API rate limits can cause request failures or delays.

  • Error Messages:

    • "The resource '...' is not implemented!" — indicates an unsupported resource was selected.
    • Errors fetching customers or other dynamic options will be logged and shown as option errors in dropdowns.
    • API request errors will surface as error messages in the node output if "Continue On Fail" is enabled.

  • Resolutions:

    • Ensure API credentials are correctly set up and have necessary permissions.
    • Provide all required parameters based on the chosen date selection method.
    • Verify customer IDs via the dynamic dropdown or API before filtering.
    • Use "Return All" cautiously to avoid large data loads; apply limits as needed.

Links and References

Discussion