Datto RMM

Interact with Datto RMM API to manage devices, sites, alerts, and monitoring

Overview

The node interacts with the Datto RMM API to retrieve default filters used for organizing and managing monitoring, maintenance, reporting, automation, and custom workflows within an organization. This operation is useful when you want to programmatically access predefined filter sets that help segment data or alerts based on categories such as Monitoring, Maintenance, Reporting, Automation, or Custom user-defined groups.

Practical examples include:

  • Automatically fetching all default filters in the "Monitoring" category to apply them in alert dashboards.
  • Retrieving paginated lists of default filters to display in a custom UI or further process them in workflow automations.
  • Selecting specific fields from the default filters to optimize data handling and reduce payload size.

Properties

Name Meaning
Category Filter category for organization and grouping. Options: All, Monitoring, Maintenance, Reporting, Automation, Custom.
Retrieve All Boolean flag indicating whether to automatically retrieve all results using pagination (true) or manually specify page and max results (false).
Page Page number to retrieve (1-based). Only applicable if "Retrieve All" is false.
Max Results Maximum number of results to return per page. Only applicable if "Retrieve All" is false.
Fields to Include Select which fields to include in the response. You can define specific fields or add all available fields related to the filter resource.

Output

The output JSON contains an array of filter objects representing the default filters retrieved from the Datto RMM API. Each filter object includes properties depending on the selected fields, such as filter name, category, UID, and other metadata relevant to the filter.

If binary data were involved (not indicated here), it would typically represent attachments or files associated with filters, but this operation focuses on JSON data only.

Dependencies

  • Requires an active connection to the Datto RMM API via an API key credential configured in n8n.
  • The node uses the base URL and authentication headers from the configured credentials.
  • Pagination support is built-in, allowing automatic retrieval of all pages or manual control over paging parameters.

Troubleshooting

  • Common issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Requesting too many results per page may lead to timeouts or rate limiting by the API.
    • Specifying invalid categories or unsupported field names may result in empty responses or errors.
  • Error messages:

    • Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
    • Pagination errors may occur if page numbers exceed available data; adjust page/max settings accordingly.
    • Network or API downtime will cause request failures; check network connectivity and Datto RMM service status.

Links and References

Discussion