Datto RMM

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

Actions53

Overview

This node integrates with the Datto RMM API to manage and retrieve information related to IT infrastructure components such as devices, sites, alerts, jobs, audits, systems, and filters. Specifically, for the Site resource with the Get Filters operation, it fetches filter configurations associated with a selected site. This is useful for scenarios where you want to programmatically obtain filtering criteria or saved views applied to a particular site within Datto RMM.

Practical examples:

  • Automatically retrieving all custom filters configured for a specific site to audit or replicate them.
  • Using site filters to dynamically adjust monitoring dashboards or reports in downstream workflows.
  • Integrating site-specific filter data into ticketing or alerting systems for enhanced context.

Properties

Name Meaning
Site Select the target site from a list of available sites. The node will operate on this site.
Fields to Return Choose which fields to include in the response. Allows customizing the output data structure.
  • The Site property uses a dynamic dropdown populated by fetching all available sites via the API.
  • The Fields to Return property lets users specify exactly which fields they want returned, optimizing data usage.

Output

The node outputs JSON data representing the filters associated with the selected site. The structure depends on the fields chosen in the "Fields to Return" property but generally includes details like filter names, categories, unique identifiers, and possibly filter criteria.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Datto RMM API using an API key credential configured in n8n.
  • The node relies on the base URL and authentication headers set in the credentials.
  • The node internally calls helper functions to perform API requests and handle pagination if needed.

Troubleshooting

  • Common issues:

    • Selecting a site that no longer exists or to which the API user lacks access may result in empty responses or errors.
    • Network connectivity problems or incorrect API credentials will cause authentication failures.
    • Misconfiguration of the "Fields to Return" property might lead to incomplete or unexpected data.

  • Error messages:

    • "Resource site is not supported yet." — indicates an unsupported resource selection; unlikely here since "site" is supported.
    • API errors such as 401 Unauthorized or 404 Not Found typically mean invalid credentials or wrong site UID.

  • Resolutions:

    • Verify API credentials and permissions.
    • Confirm the selected site exists and is accessible.
    • Adjust the "Fields to Return" settings to valid field names.

Links and References

Discussion