Actions22
- Agent Actions
- Alert Actions
- Client Actions
- Software Actions
Overview
This node integrates with the Tactical RMM API to retrieve information about agents associated with a specific client. The "Get By Client" operation under the "Agent" resource fetches a list of agents filtered by the selected client. This is useful in scenarios where you want to manage or monitor devices (agents) deployed for a particular client, such as generating reports, performing bulk updates, or monitoring agent status.
Practical examples:
- Fetch all agents installed for a given client to check their online/offline status.
- Retrieve agent details to automate patch management or software deployment per client.
- Use the agent list to trigger alerts or notifications based on client-specific device conditions.
Properties
| Name | Meaning |
|---|---|
| Client Name or ID | Select a client from a dropdown list or specify its ID using an expression. This identifies which client's agents to retrieve. |
| Limit | Maximum number of agent records to return. Must be at least 1. Defaults to 50. |
Output
The node outputs JSON data containing an array of agent objects related to the specified client. Each agent object typically includes details such as agent ID, name, status, and other metadata provided by the Tactical RMM API.
If the node supports binary data output (not indicated here), it would represent files or attachments related to agents, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Tactical RMM API via an API key credential configured in n8n.
- The node depends on the Tactical RMM API being accessible and the user having appropriate permissions to query agent data.
- The
getClientsmethod is used internally to load client options dynamically.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Specifying a client ID that does not exist or has no agents will result in empty results.
- Network connectivity problems can prevent the node from reaching the Tactical RMM API.
Error messages:
- Authentication errors usually indicate invalid or expired API keys; verify and update credentials.
- "No agents found" or empty responses suggest checking the client selection or verifying that agents are assigned to the client.
- Timeout or network errors require checking internet connectivity and API endpoint availability.