Actions12
Overview
The "Reboot Agent" operation in this node allows users to remotely reboot a specific agent managed by the Tactical RMM system via its API. This is useful for IT administrators or managed service providers who need to restart machines or devices (agents) to apply updates, resolve issues, or perform maintenance without direct physical access.
Practical examples:
- Automatically reboot an agent after deploying critical software updates.
- Schedule reboots of agents during off-hours to minimize disruption.
- Trigger a reboot as part of a recovery workflow when an agent becomes unresponsive.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent to reboot. |
Output
The node outputs the JSON response returned by 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.
No binary data output is involved.
Dependencies
- Requires an active connection to the Tactical RMM API.
- Needs an API key credential configured in n8n for authentication with the Tactical RMM service.
- The base URL of the Tactical RMM API must be correctly set in the credentials.
Troubleshooting
Common issues:
- Invalid or missing Agent ID will cause the API call to fail.
- Incorrect or expired API key will result in authentication errors.
- Network connectivity problems can prevent reaching the Tactical RMM API endpoint.
Error messages:
- Authentication errors typically indicate invalid API credentials; verify and update the API key.
- "Agent not found" errors suggest the provided Agent ID does not exist; confirm the correct ID.
- Timeout or network errors require checking internet connectivity and API availability.
Links and References
- Tactical RMM official API documentation (refer to their website or developer portal for detailed API endpoints and usage).