Actions12
Overview
The node interacts with the Tactical RMM API specifically for managing agents and their related data. The "Get Agent Checks" operation retrieves the health or status checks associated with a specific agent identified by its ID. This is useful in scenarios where you want to monitor or audit the current state of an agent, such as checking if certain services are running, verifying system metrics, or ensuring compliance with monitoring policies.
Practical examples include:
- Automatically fetching agent check results to trigger alerts or notifications.
- Integrating agent health data into dashboards or reporting tools.
- Periodically auditing agent statuses as part of maintenance workflows.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent whose checks you want to retrieve. |
Output
The output is a JSON array containing the data returned from the Tactical RMM API endpoint for agent checks. This typically includes details about each check performed on the specified agent, such as check names, statuses, timestamps, and possibly additional metadata depending on the API response structure.
No binary data output is involved in this operation.
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 configured within the credentials.
- Network access to the Tactical RMM API endpoint must be available.
Troubleshooting
Common issues:
- Invalid or missing Agent ID will result in API errors or empty responses.
- Incorrect or expired API key credentials will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
- API errors thrown by the node will be wrapped and presented as node execution errors.
- Typical error messages may include HTTP 401 Unauthorized (invalid API key), 404 Not Found (agent ID does not exist), or 500 Internal Server Error (server-side issues).
Resolutions:
- Verify that the Agent ID is correct and corresponds to an existing agent.
- Ensure the API key credential is valid and has necessary permissions.
- Check network connectivity and firewall settings allowing access to the Tactical RMM API.
Links and References
- Tactical RMM official API documentation (refer to the agent checks endpoint)
- n8n documentation on creating and using API credentials