Actions12
Overview
This node interacts with the Tactical RMM API specifically for managing Agents. It allows users to perform various operations on agents such as retrieving agent details, updating, deleting, running scripts, rebooting, and fetching related data like checks, event logs, tasks, and pending actions.
The Get Agent by ID operation fetches detailed information about a specific agent using its unique identifier. This is useful in scenarios where you want to retrieve the current state or configuration of an individual agent within your remote monitoring and management setup.
Practical examples:
- Fetching an agent's details before performing an update.
- Retrieving agent information to display in a dashboard or report.
- Verifying agent status or metadata before triggering automated workflows.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent to operate on. This must be provided to specify which agent to get, update, delete, or perform other operations on. |
Output
The output is a JSON array containing the response from the Tactical RMM API for the requested operation. For the Get Agent by ID operation, the JSON will include detailed information about the specified agent, such as its properties, status, configuration, and any other metadata returned by the API.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Tactical RMM API.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL for the Tactical RMM API must be set in the credentials.
Troubleshooting
Common issues:
- Invalid or missing Agent ID: Ensure the Agent ID is correctly provided; otherwise, the API call will fail.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or connectivity problems: Confirm that the base URL is reachable from the n8n environment.
Error messages:
- API errors are wrapped and thrown as node errors. For example, if the agent does not exist, the API might return a 404 error, which will be surfaced by the node.
- If the API key is invalid or missing, authentication errors will occur.
To resolve these, double-check input parameters, credentials, and network access.
Links and References
- Tactical RMM Official Documentation (for API details and agent management)
- n8n Documentation (for general usage of HTTP request nodes and credentials)