Datto RMM

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

Overview

The node enables interaction with the Datto RMM platform to create custom filters that can be applied to various resource types such as devices, sites, alerts, or a combination thereof. Creating filters allows users to define criteria for selecting subsets of resources based on attributes like hostname patterns or operating system types.

This is useful in scenarios where you want to segment your managed environment for monitoring, reporting, automation, or maintenance tasks. For example, you might create a filter named "Windows Servers" with criteria targeting devices running Windows OS and hostnames starting with "server-". This filter can then be reused across workflows to focus actions only on those devices.

Properties

Name Meaning
Filter Name The name assigned to the new custom filter.
Description Optional textual description providing details about the filter's purpose or usage.
Filter Criteria A JSON object defining the conditions that resources must meet to be included in the filter. For example: {"hostname": "server-*", "operatingSystem": "Windows"}.
Filter Type The type of resource the filter applies to. Options: Device, Site, Alert, Mixed (combines multiple resource types).
Category Organizational category for the filter. Options include All, Monitoring, Maintenance, Reporting, Automation, Custom.

Output

The node outputs JSON data representing the created filter object. This typically includes fields such as the filter's unique identifier, name, description, criteria, type, and category. The output can be used downstream in workflows to reference or apply the newly created filter.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating with the Datto RMM API.
  • The node uses the base URL and authentication headers configured via the provided credentials.
  • No additional external dependencies are required beyond the Datto RMM API access.

Troubleshooting

  • Invalid Filter Criteria JSON: If the JSON provided in the Filter Criteria property is malformed or does not conform to expected schema, the API may reject the request. Ensure the JSON is valid and correctly structured.
  • Missing Required Fields: The Filter Name and Filter Criteria are mandatory. Omitting these will cause errors.
  • API Authentication Errors: Ensure the API key credential is valid and has sufficient permissions to create filters.
  • Unsupported Filter Type or Category: Using values outside the provided options may result in errors.
  • Network Issues: Connectivity problems with the Datto RMM API endpoint will prevent filter creation.

Common error messages usually indicate missing parameters, invalid JSON, or authorization failures. Reviewing the node’s input parameters and credentials setup typically resolves these issues.

Links and References

Discussion