Actions7
Overview
This node interacts with the Tactical RMM API specifically for managing Alerts. It supports various operations such as creating, retrieving, updating, deleting alerts, and handling alert templates. The "Delete Alert" operation allows users to remove an alert by specifying its unique ID.
Common scenarios include automating alert management within IT monitoring workflows, such as automatically deleting obsolete or resolved alerts, or integrating alert lifecycle management into broader automation pipelines.
Example use case: Automatically delete alerts that have been acknowledged or resolved in an external system to keep the alert list clean and relevant.
Properties
| Name | Meaning |
|---|---|
| Alert ID | The ID of the alert to delete. |
Output
The node outputs a JSON array containing the response from the Tactical RMM API after performing the delete operation. This typically includes confirmation of deletion or details about the deleted alert. No binary data is output by this node.
Dependencies
- Requires an API key credential for authenticating with the Tactical RMM API.
- The node expects the base URL of the Tactical RMM API to be provided via credentials.
- Network access to the Tactical RMM API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Alert ID will cause the API call to fail.
- Incorrect or expired API key will result in authentication errors.
- Network connectivity problems can prevent successful API requests.
Error messages:
- Authentication errors usually indicate invalid API credentials; verify and update the API key.
- "Not Found" errors may mean the specified Alert ID does not exist; confirm the alert ID is correct.
- General request failures might require checking network connectivity or API availability.
Links and References
- Tactical RMM official API documentation (refer to Alerts section)
- n8n documentation on using HTTP Request nodes and API integrations