Datto RMM

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

Actions53

Overview

The node interacts with the Datto RMM API to manage filters, specifically allowing users to update existing filters. Filters in Datto RMM are used to define criteria for selecting devices, sites, alerts, or combinations thereof, which can then be applied in monitoring, maintenance, reporting, automation, and other workflows. This node operation is beneficial when you need to modify an existing filter's properties such as its name, description, criteria, type, or category without recreating it from scratch.

Practical examples include:

  • Renaming a device filter to better reflect its purpose.
  • Updating the JSON criteria of an alert filter to refine which alerts are included.
  • Changing the category of a filter to reorganize it within your system.

Properties

Name Meaning
Filter ID The unique identifier of the filter to update.
Filter Name New name for the filter (leave empty to keep current name).
Description Description for the filter.
Filter Criteria Updated JSON object defining the filter criteria (leave empty to keep current criteria).
Filter Type Type of resource this filter applies to. Options: Device, Site, Alert, Mixed (combines multiple types).
Category Filter category for organization and grouping. Options: All, Monitoring, Maintenance, Reporting, Automation, Custom.

Output

The node outputs JSON data representing the updated filter object as returned by the Datto RMM API. This typically includes fields such as the filter's unique ID, name, description, criteria, type, category, and possibly metadata like creation or modification timestamps.

No binary data output is involved in this operation.

Dependencies

  • Requires an active connection to the Datto RMM API via an API key credential configured in n8n.
  • The node depends on the Datto RMM API endpoint for filters to perform update operations.
  • Proper permissions on the API key to update filters are necessary.

Troubleshooting

  • Common Issues:

    • Providing an invalid or non-existent Filter ID will result in errors indicating the filter could not be found.
    • Malformed JSON in the Filter Criteria property may cause the API to reject the request.
    • Insufficient API permissions can lead to authorization errors.
    • Network connectivity issues between n8n and the Datto RMM API can cause timeouts or failures.

  • Error Messages and Resolutions:

    • "Filter not found": Verify that the Filter ID is correct and that the filter exists.
    • "Invalid JSON format": Ensure the Filter Criteria JSON is well-formed and valid.
    • "Unauthorized" or "Forbidden": Check that the API key has the required permissions to update filters.
    • "Network Error": Confirm network connectivity and API URL configuration in credentials.

Links and References

Discussion