Tactical RMM Agents icon

Tactical RMM Agents

Interact with the Tactical RMM API for Agents

Actions12

Overview

The node interacts with the Tactical RMM (Remote Monitoring and Management) API specifically for managing agents. The "Delete Agent" operation allows users to remove an agent from the Tactical RMM system by specifying its unique Agent ID. This is useful in scenarios where an agent is no longer needed, has been decommissioned, or needs to be removed due to security or maintenance reasons.

Practical example:

  • Automatically deleting agents that have been offline for a prolonged period.
  • Cleaning up test or temporary agents after deployment validation.

Properties

Name Meaning
Agent ID The unique identifier of the agent to delete

Output

The output is a JSON array containing the response from the Tactical RMM API after attempting to delete the specified agent. Typically, this will include confirmation of deletion or details about any error encountered.

No binary data is output by this node.

Example output structure (simplified):

[
  {
    "detail": "Agent deleted successfully"
  }
]

Dependencies

  • Requires an active connection to the Tactical RMM API via an API key credential.
  • The node expects the base URL and API key for the Tactical RMM instance to be configured in the credentials.
  • Network access to the Tactical RMM API endpoint must be available.

Troubleshooting

  • Common issues:

    • Invalid or missing Agent ID: The API call will fail if the Agent ID is not provided or incorrect.
    • Authentication errors: If the API key is invalid or expired, the request will be rejected.
    • Network connectivity problems: Unable to reach the Tactical RMM API endpoint.

  • Error messages:

    • NodeApiError: This generic error wraps API response errors. Check the error message for details such as "Agent not found" or "Unauthorized".

  • Resolutions:

    • Verify the Agent ID is correct and exists in the Tactical RMM system.
    • Ensure the API key credential is valid and has sufficient permissions.
    • Confirm network connectivity and that the base URL is correctly set.

Links and References

Discussion