Tactical RMM Agents icon

Tactical RMM Agents

Interact with the Tactical RMM API for Agents

Overview

The "Get Agent History" operation in the Tactical RMM Agents node retrieves the historical data related to a specific agent from the Tactical RMM API. This history typically includes logs or records of actions, events, or changes associated with the agent over time.

This node is beneficial in scenarios where users need to audit agent activity, troubleshoot issues by reviewing past events, or analyze agent behavior and performance trends. For example, a system administrator might use this operation to fetch an agent's history to investigate why a particular task failed or to verify that updates were applied correctly.

Properties

Name Meaning
Agent ID The unique identifier of the agent whose history you want to retrieve.

Output

The output is a JSON array containing the agent's history data as returned by the Tactical RMM API. This data structure typically includes entries representing individual historical records such as events, status changes, or other relevant logs tied to the agent.

No binary data is output by this operation.

Dependencies

  • Requires an active connection to the Tactical RMM API.
  • Requires an API key credential for authentication, which must be configured in n8n.
  • The base URL of the Tactical RMM API must be set in the credentials.

Troubleshooting

  • Common Issues:

    • Invalid or missing Agent ID: Ensure the Agent ID provided is correct and corresponds to an existing agent.
    • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
    • Network or connectivity problems: Confirm that the Tactical RMM API endpoint is reachable from the n8n instance.
  • Error Messages:

    • API request failures will throw errors wrapped as NodeApiError with details from the Tactical RMM API response.
    • If the agent does not exist or the ID is incorrect, the API may return a 404 error.

To resolve these errors:

  • Double-check the Agent ID input.
  • Validate API credentials.
  • Review network settings and firewall rules.

Links and References

Discussion