Actions7
Overview
The node interacts with the Tactical RMM API specifically for managing Alerts. It supports various operations such as creating, retrieving, updating, deleting alerts, and working with alert templates. This node is useful in IT management workflows where automated monitoring and alerting of remote machines are required. For example, it can be used to update an existing alert's details based on new conditions or to fetch alert information by ID for reporting purposes.
Properties
| Name | Meaning |
|---|---|
| Alert ID | The unique numeric identifier of the alert to get, update, or delete. |
Output
The node outputs a JSON array containing the response from the Tactical RMM API corresponding to the performed operation. The structure of the JSON depends on the API endpoint called but generally includes alert details such as alert metadata, status, and related information. There is no binary data output.
Dependencies
- Requires an API key credential for authenticating with the Tactical RMM API.
- The base URL for the Tactical RMM API must be configured in the credentials.
- The node uses HTTP methods (GET, POST, PUT, PATCH, DELETE) to interact with the API endpoints.
Troubleshooting
- Common issues:
- Invalid or missing API key will cause authentication failures.
- Providing an incorrect Alert ID may result in "not found" errors.
- Network connectivity problems can prevent successful API calls.
- Error messages:
- Errors thrown by the node include detailed API error responses wrapped in a NodeApiError.
- To resolve, verify API credentials, ensure the Alert ID exists, and check network access to the Tactical RMM server.
Links and References
- Tactical RMM official API documentation (refer to your Tactical RMM installation or vendor resources for exact URLs).