Tactical RMM icon

Tactical RMM

Get data from the TacticalRMM API

Actions22

Overview

This node integrates with the Tactical RMM API to retrieve event logs for a specified agent. It is useful in IT management and monitoring scenarios where administrators need to audit or review system events such as application errors, security alerts, or system messages on managed endpoints. For example, an IT technician can use this node to fetch recent application error logs from a particular agent to diagnose software issues or track security-related events for compliance auditing.

Properties

Name Meaning
Agent ID The unique identifier of the agent whose event log you want to retrieve.
Log Name The type of event log to retrieve. Options: Application, System, Security.
Days Number of days to look back when fetching events (e.g., 1 means events from the last day).
Limit Maximum number of event log entries to return (minimum value is 1).

Output

The node outputs JSON data containing the retrieved event log entries for the specified agent. Each entry typically includes details such as event timestamps, event IDs, source names, event levels, and descriptive messages related to the events in the chosen log (Application, System, or Security).

If the node supports binary data output (not explicitly shown here), it would likely represent raw event log files or attachments, but based on the provided code and properties, the output is primarily structured JSON event data.

Dependencies

  • Requires an active connection to the Tactical RMM API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The node depends on internal routing logic (actions/router) to handle the execution flow and API calls.

Troubleshooting

  • Common Issues:

    • Invalid or missing Agent ID will result in failure to retrieve logs.
    • Requesting logs for too many days or setting a very high limit might cause performance delays or API rate limiting.
    • Incorrect API credentials or expired tokens will cause authentication errors.

  • Error Messages:

    • Authentication errors indicate invalid or missing API keys; verify and update credentials.
    • "Agent not found" or similar errors suggest the provided Agent ID does not exist or is inaccessible.
    • Rate limit exceeded errors require reducing request frequency or limits.

Links and References

Discussion