Druva MSP icon

Druva MSP

Interact with the Druva MSP API
Join our community

Actions39

Overview

The "Get Many" operation for the Service Plan resource in this node retrieves multiple service plans from the Druva MSP API. It supports filtering by various criteria such as edition, features, name substring, and status, and allows users to control how many results are returned or to fetch all available results.

This operation is useful when you want to list or analyze multiple service plans at once, for example:

  • Displaying all available service plans for a customer or tenant.
  • Filtering service plans to find those that match specific editions or include certain features.
  • Searching for service plans by partial name matches.
  • Retrieving active or inactive service plans based on their status.

Practical examples:

  • An MSP administrator wants to generate a report of all Enterprise edition service plans currently active.
  • A support engineer needs to find all service plans that include a particular feature to troubleshoot customer issues.
  • A billing system integration requires fetching all service plans up to a certain limit for synchronization.

Properties

Name Meaning
Return All Whether to return all matching service plans or only up to a specified limit.
Limit Maximum number of service plans to return (only used if "Return All" is false).
Filter by Edition Whether to filter service plans by their edition type.
Editions List of editions to filter by (e.g., Business, Enterprise, Elite).
Filter by Feature Whether to filter service plans by available features.
Features List of features to filter service plans by.
Filter by Name Whether to filter service plans by name substring.
Name Contains Text substring to filter service plan names (case-insensitive).
Filter by Status Whether to filter service plans by their status.
Status The status to filter service plans by (e.g., Active, Inactive).

Output

The output is an array of JSON objects representing the retrieved service plans. Each object contains details about a service plan as returned by the Druva MSP API. The exact fields depend on the API response but typically include identifiers, names, editions, features, and status information.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the Druva MSP API.
  • The node uses the base URL https://apis.druva.com for API requests.
  • Pagination and filtering are handled internally via API query parameters.
  • The node depends on internal helper functions to request all items and load options dynamically for dropdowns.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Using filters with invalid values may result in empty responses or errors.
    • Network connectivity issues can prevent successful API calls.
    • Exceeding API rate limits may cause temporary request failures.

  • Error Messages:

    • Errors related to fetching service plans will include messages like "Error fetching service plans: [details]".
    • If the resource or operation is not implemented, an error stating "The resource 'servicePlan' is not implemented!" will be thrown.

  • Resolutions:

    • Verify that the API key credential is correctly configured and has necessary permissions.
    • Double-check filter values against allowed options.
    • Ensure stable network connection.
    • Implement retry logic or respect API rate limits.

Links and References

Discussion