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 manage alerts, specifically allowing users to mute alerts. Muting an alert temporarily suppresses notifications or actions related to that alert without resolving or deleting it. This is useful in scenarios where an alert is known and being addressed, or when you want to prevent alert noise during maintenance windows.
For example, if a device generates a recurring alert that is already under investigation, muting the alert prevents repeated notifications while work is ongoing.
Properties
| Name | Meaning |
|---|---|
| Alert | Select the specific open alert to mute from a dynamically loaded list of current open alerts |
The "Alert" property uses a dropdown populated by fetching all currently open alerts from the Datto RMM system, showing alert type, device name, and priority for easy identification.
Output
The node outputs JSON data representing the result of the mute operation on the selected alert. This typically includes confirmation details such as the alert's unique identifier and its updated status indicating it is muted.
No binary data output is involved.
Dependencies
- Requires an active connection to the Datto RMM API.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The node relies on the Datto RMM API endpoint
/api/v2/account/alerts/opento fetch open alerts and the corresponding API call to mute the selected alert.
Troubleshooting
Common issues:
- Failure to load open alerts: Usually caused by network issues or invalid API credentials.
- Error muting alert: May occur if the alert UID is invalid or the alert is no longer open.
Error messages:
- "Resource alert is not supported yet": Indicates a misconfiguration or unsupported resource selection.
- API errors related to authorization: Check that the API key credential is correctly set up and has sufficient permissions.
Resolutions:
- Verify API credentials and connectivity.
- Ensure the alert selected is currently open and valid.
- Refresh the alert list before selecting to avoid stale UIDs.