Actions12
Overview
The node interacts with the Tactical RMM (Remote Monitoring and Management) API specifically for managing agents. The "Recover Agent" operation sends a request to recover a specified agent by its ID. This is useful in scenarios where an agent on a remote machine needs to be restored or brought back to a healthy state after failure or disconnection.
Practical examples:
- Automatically recovering an agent that has stopped responding.
- Integrating recovery actions into automated workflows for system maintenance.
- Triggering recovery after detecting issues from monitoring data.
Properties
| Name | Meaning |
|---|---|
| Agent ID | The unique identifier of the agent to recover. |
Output
The output is a JSON object representing the response from the Tactical RMM API after attempting to recover the agent. It typically contains status information about the recovery request, such as success confirmation or error details.
No binary data is output by this operation.
Dependencies
- Requires an active connection to the Tactical RMM API.
- Needs an API key credential configured in n8n for authentication.
- The base URL of the Tactical RMM API must be set in the credentials.
Troubleshooting
- Common issue: Invalid or missing Agent ID will cause the API call to fail.
- Resolution: Ensure the Agent ID is correctly provided and corresponds to an existing agent.
- API authentication errors: If the API key is invalid or missing, requests will be rejected.
- Resolution: Verify the API key credential configuration in n8n.
- Network or connectivity problems: Failure to reach the Tactical RMM API endpoint.
- Resolution: Check network access and the correctness of the base URL.
- Error messages: The node throws errors wrapped as API errors with details from the Tactical RMM API response.
- Resolution: Review the error message for specific API error codes or messages and adjust inputs accordingly.
Links and References
- Tactical RMM official documentation: https://tacticalrmm.io/docs/
- Tactical RMM API reference (if publicly available) for detailed endpoints and payloads.