Actions22
- Agent Actions
- Alert Actions
- Client Actions
- Software Actions
Overview
This node integrates with the Tactical RMM API to perform various operations on managed resources. Specifically, the "Agent" resource's "Reboot" operation allows users to remotely reboot an agent machine managed by Tactical RMM. This is useful for system administrators who need to restart machines for updates, troubleshooting, or maintenance without direct physical access.
Practical examples include:
- Forcing a reboot of an agent that is unresponsive or stuck.
- Scheduling a delayed reboot to allow users to save work before the system restarts.
- Performing routine reboots after software installations or configuration changes.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent machine to reboot. |
| Force Reboot | Whether to force the reboot immediately without waiting for applications to close. |
| Delay (Seconds) | Number of seconds to wait before initiating the reboot (range: 0 to 3600 seconds). |
Output
The node outputs JSON data representing the response from the Tactical RMM API after attempting to reboot the specified agent. This typically includes status information about the reboot request, such as success confirmation or error details.
If the node supports binary data output, it would generally relate to logs or files returned by the API, but based on the provided code and context, the output is JSON only.
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 modules handling different resource actions and routing logic, which manage communication with the Tactical RMM backend.
Troubleshooting
Common issues:
- Invalid or missing Agent ID will cause the reboot request to fail.
- Insufficient permissions or invalid API credentials can result in authorization errors.
- Setting a delay outside the allowed range (0-3600) may cause validation errors.
Error messages:
- "Agent not found" indicates the specified Agent ID does not exist.
- "Unauthorized" or "Authentication failed" suggests problems with the API key or credential setup.
- "Invalid delay value" means the delay parameter is out of bounds.
To resolve these, verify the Agent ID correctness, ensure valid API credentials are configured, and confirm the delay value is within the accepted range.