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 retrieve information about sites, devices, alerts, and other resources managed within Datto RMM. Specifically, for the Site resource with the Get Resolved Alerts operation, it fetches resolved alerts associated with a selected site. This is useful for monitoring historical alert data, auditing past issues, or generating reports on resolved incidents.

Practical scenarios include:

  • Automatically retrieving all resolved alerts for a specific site to analyze trends in device issues.
  • Filtering resolved alerts by whether they were muted or not.
  • Paginating through large sets of resolved alerts when there are many entries.

Properties

Name Meaning
Site Select the site from which to retrieve resolved alerts. The list is dynamically loaded from available sites.
Retrieve All Whether to automatically retrieve all resolved alerts using pagination (true), or manually specify page and max results (false).
Page When not retrieving all, specifies the page number of results to fetch.
Max Results When not retrieving all, specifies the maximum number of resolved alerts to return per page.
Muted Include muted alerts in the results if set to true; otherwise, exclude them.
Fields to Return Select which fields to include in the response for each alert, allowing customization of output data.

Output

The node outputs JSON data representing the resolved alerts retrieved from the specified site. Each alert object includes fields as selected by the user in the "Fields to Return" property. Typical fields may include alert type, device name, priority, resolution details, timestamps, and mute status.

If binary data were involved (not indicated here), it would be summarized accordingly, but this operation deals with JSON alert 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 provided credentials.
  • Pagination support depends on the API's ability to return paged results.
  • Dynamic loading of options (sites, alerts) relies on helper methods that call the Datto RMM API endpoints.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Selecting a site with no resolved alerts will result in empty output.
    • Pagination parameters must be valid numbers; invalid values may cause errors or unexpected results.
    • Network connectivity issues can prevent API calls from succeeding.

  • Error Messages:

    • Errors related to unsupported resources or operations indicate misconfiguration of the node parameters.
    • API rate limits or permission errors from Datto RMM will surface as HTTP errors; ensure the API key has sufficient permissions.
    • If dynamic option loading fails (e.g., sites list), check API access and network connectivity.

Links and References

Discussion