Tactical RMM icon

Tactical RMM

Get data from the TacticalRMM API

Actions22

Overview

This node integrates with the Tactical RMM API to retrieve information about processes running on a specified agent (a managed device). The "Get Processes" operation under the "Agent" resource fetches a list of active processes from the targeted agent. This is useful for monitoring system activity, troubleshooting performance issues, or auditing running software on remote machines.

Practical examples include:

  • Fetching currently running processes on a server to detect unauthorized applications.
  • Monitoring resource usage by analyzing process lists periodically.
  • Integrating with automation workflows that respond to specific processes being active or inactive.

Properties

Name Meaning
Agent ID The unique identifier of the agent (device) from which to retrieve the list of processes.
Limit Maximum number of process entries to return. Must be at least 1. Defaults to 50.

Output

The node outputs JSON data containing an array of process objects retrieved from the specified agent. Each object typically includes details such as process name, ID, CPU and memory usage, and other relevant metadata depending on the Tactical RMM API response.

If the node supports binary data output (not indicated in the provided code), it would generally represent files or logs related to processes, but this is not evident here.

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 the Tactical RMM service being accessible and the specified agent existing within that system.

Troubleshooting

  • Common Issues:

    • Invalid or missing Agent ID will cause the request to fail or return no data.
    • Network connectivity problems or incorrect API credentials can lead to authentication errors.
    • Requesting a very high limit might result in timeouts or partial data retrieval depending on API constraints.

  • Error Messages:

    • Authentication failures usually indicate invalid or expired API tokens; reconfigure credentials.
    • "Agent not found" errors suggest the provided Agent ID does not exist or is mistyped.
    • Rate limiting or quota exceeded errors require checking API usage limits and possibly adjusting request frequency.

Links and References

Discussion