Actions22
- Agent Actions
- Alert Actions
- Client Actions
- Software Actions
Overview
This node integrates with the Tactical RMM API to retrieve historical data related to agents. Specifically, the "Get History" operation for the "Agent" resource fetches the activity or event history of a specified agent within a defined time period. This is useful for monitoring agent performance, troubleshooting issues, auditing changes, or analyzing agent behavior over recent days.
Practical examples include:
- Retrieving the last 7 days of an agent's activity to investigate recent alerts or errors.
- Fetching the last 24 hours of history to monitor real-time agent status.
- Limiting the number of returned records to focus on the most recent events.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent whose history you want to retrieve. |
| Time Filter | The time range for which to retrieve history. Options: Last 24 Hours, 7 Days, 30 Days, 90 Days. |
| Limit | Maximum number of history records to return. Minimum value is 1. |
Output
The node outputs JSON data containing the agent's history records matching the specified criteria. Each record typically includes details such as timestamps, event types, descriptions, and other relevant metadata about the agent's activities during the selected time frame.
If the node supports binary data output (not indicated in the provided code), it would represent attachments or logs related to the agent's history, but this is not evident here.
Dependencies
- Requires connection to the Tactical RMM API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node uses standard HTTP headers to request JSON data from the API.
Troubleshooting
- Invalid Agent ID: If the provided Agent ID does not exist or is incorrect, the API may return an error or empty results. Verify the Agent ID before running the node.
- API Authentication Errors: Missing or invalid API credentials will cause authentication failures. Ensure the API key/token is correctly set up in n8n.
- Rate Limits or Timeouts: Large requests or frequent polling might hit API rate limits or cause timeouts. Adjust the "Limit" property or polling frequency accordingly.
- Empty Results: If no history is found for the given time filter, verify that the agent has activity in that period or try expanding the time range.
Links and References
- Tactical RMM official API documentation (refer to their website or developer portal for detailed API specs).
- n8n documentation on creating and using API credential nodes.
- General REST API usage guidelines for handling authentication and pagination.