Actions22
- Agent Actions
- Alert Actions
- Client Actions
- Software Actions
Overview
This node integrates with the Tactical RMM API to retrieve monitoring checks associated with a specific agent. It is useful in scenarios where you want to programmatically access the health or status checks configured for an agent within the Tactical RMM system. For example, you might use this node to fetch recent check results for an agent to display in a dashboard or trigger alerts based on their statuses.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent from which to retrieve monitoring checks. |
| Limit | The maximum number of check results to return. Defaults to 50; minimum value is 1. |
Output
The node outputs JSON data containing the list of monitoring checks retrieved for the specified agent. Each item in the output typically represents a single check with its details such as status, name, last run time, and other relevant metadata. There is no indication that binary data is returned by this node.
Dependencies
- Requires an API key credential for authenticating with the Tactical RMM API.
- The node expects the Tactical RMM API to be accessible and properly configured.
- No additional external dependencies are indicated beyond the API connection.
Troubleshooting
- Common issues:
- Invalid or missing Agent ID will result in errors or empty responses.
- API authentication failures due to incorrect or expired credentials.
- Network connectivity problems preventing access to the Tactical RMM API.
- Error messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Agent not found" or similar errors suggest the provided Agent ID does not exist.
- Rate limiting or timeout errors may require retry logic or adjusting the limit parameter.
Links and References
- Tactical RMM official API documentation (refer to the vendor's site for detailed API specs).
- n8n documentation on creating and using API credentials.