Actions53
- Account Actions
- Device Actions
- Site Actions
- Alert Actions
- Job Actions
- Audit Actions
- System Actions
- Filter Actions
Overview
The node interacts with the Datto RMM API to retrieve information about devices and their alerts. Specifically, for the Device resource and the Get Resolved Alerts operation, it fetches alerts that have been resolved on a selected device. This is useful for monitoring historical alert data, auditing past issues, or generating reports on device health and incident resolution.
Typical use cases include:
- Automatically retrieving all resolved alerts for a device to analyze trends or recurring problems.
- Paginating through resolved alerts when dealing with large volumes of alert data.
- Including muted alerts in the results to get a comprehensive view of all resolved notifications.
Properties
| Name | Meaning |
|---|---|
| Device | Select the specific device from which to retrieve resolved alerts. The list is dynamically loaded. |
| Retrieve All | Whether to automatically retrieve all resolved alerts using pagination (true), or manually specify page and max results (false). |
| Page | (Shown if "Retrieve All" is false) The page number of results to retrieve. |
| Max Results | (Shown if "Retrieve All" is false) Maximum number of resolved alerts to return per page. |
| Include Muted Alerts | Whether to include muted resolved alerts in the results (true or false). |
Output
The node outputs JSON data containing an array of resolved alerts for the specified device. Each alert object typically includes details such as alert type, device name, priority, timestamps, and status indicating resolution.
If binary data were involved (e.g., attachments), it would be summarized here, but this operation focuses on JSON alert data only.
Dependencies
- Requires an active connection to the Datto RMM API via an API key credential configured in n8n.
- The base URL for the API is taken from the credential configuration.
- Pagination support depends on the API's pagination mechanism.
- Dynamic loading of device options requires API access to list devices.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication errors.
- Selecting a device that no longer exists or has no resolved alerts may return empty results.
- Pagination parameters out of range may result in no data or errors.
Error Messages:
- Authentication failures: Check API key validity and permissions.
- Resource not supported: Ensure the resource and operation names are correct.
- Network or API errors: Verify network connectivity and API endpoint availability.
Resolutions:
- Reconfigure or update API credentials.
- Confirm device UID selection is valid.
- Adjust pagination settings or enable "Retrieve All" to avoid manual paging issues.