Actions53
- Account Actions
- Device Actions
- Site Actions
- Alert Actions
- Job Actions
- Audit Actions
- System Actions
- Filter Actions
Overview
This node interacts with the Datto RMM API to retrieve open alerts for a specified site. It is useful for IT administrators and managed service providers who want to monitor active issues or warnings on devices within a particular site managed by Datto RMM. By fetching open alerts, users can automate alert monitoring workflows, trigger notifications, or integrate alert data into broader incident management systems.
For example, an MSP could use this node to automatically pull all current open alerts from a client’s site and then create tickets in their helpdesk system for any critical alerts.
Properties
| Name | Meaning |
|---|---|
| Site | Select the specific site from which to retrieve open alerts. The list is dynamically loaded from available sites. |
| Retrieve All | Whether to automatically retrieve all results using pagination (true) or manually specify page and max results (false). |
| Page | If not retrieving all, specifies the page number of results to fetch. |
| Max Results | If not retrieving all, specifies the maximum number of results to return per page. |
| Muted | Whether to include muted alerts in the results (true to include, false to exclude). |
| Fields to Return | Allows selection of specific fields to include in the response, enabling customization of output data. |
Output
The node outputs JSON data containing the list of open alerts for the selected site. Each alert object typically includes details such as alert type, device name, priority, and other relevant metadata depending on the selected fields.
If binary data were involved (not indicated here), it would represent attachments or files related to alerts, but this node focuses on JSON alert data only.
Dependencies
- Requires an API key credential for authenticating with the Datto RMM API.
- Needs proper configuration of the API base URL in the node credentials.
- Relies on the Datto RMM API endpoints for sites and alerts.
- Pagination support depends on the API's ability to return paged results.
Troubleshooting
Common Issues:
- Incorrect or missing API credentials will cause authentication failures.
- Selecting a site that does not exist or has no open alerts will result in empty output.
- Network connectivity issues may prevent API calls from succeeding.
- Misconfiguration of pagination parameters (page number or max results) might lead to incomplete data retrieval.
Error Messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- "Resource site is not supported" error suggests a misconfiguration or unsupported resource selection.
- API rate limiting errors require waiting or adjusting request frequency.