Tactical RMM Agents

Overview

This node interacts with the Tactical RMM (Remote Monitoring and Management) API specifically for managing agents. The "Patch Reboot Agent" operation sends a PATCH request to trigger a reboot action on a specified agent. This is useful in scenarios where you want to remotely reboot an agent machine without fully deleting or recreating it, allowing for maintenance or troubleshooting tasks.

Practical examples:

• Remotely rebooting an agent after applying updates or patches.
• Triggering a reboot to resolve temporary issues on the agent device.
• Automating reboot sequences as part of a larger workflow for system management.

Properties

Output

The output is a JSON array containing the response from the Tactical RMM API after attempting the patch reboot operation. The structure depends on the API's response but generally includes status information about the reboot request.

No binary data is output 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 will cause the API call to fail.
  • Incorrect or expired API key will result in authentication errors.
  • Network connectivity issues can prevent reaching the Tactical RMM API endpoint.

• Error Messages:

  • Authentication errors typically indicate problems with the API key; verify and update credentials.
  • 404 Not Found errors may mean the specified Agent ID does not exist.
  • 400 Bad Request errors could indicate malformed requests or missing required parameters.

Resolving these usually involves verifying the Agent ID, ensuring valid API credentials, and checking network access to the Tactical RMM service.

Links and References

• Tactical RMM Official Documentation (for API details and usage)
• n8n Documentation on HTTP Request Node (conceptual similarity)