Tactical RMM icon

Tactical RMM

Get data from the TacticalRMM API

Overview

This node integrates with the Tactical RMM API to retrieve information related to agents, clients, alerts, and software. Specifically, for the "Agent" resource with the "Get Tasks" operation, it fetches a list of tasks assigned to a specified agent. This is useful in scenarios where you want to monitor or manage tasks associated with remote monitoring and management agents, such as automating task tracking, reporting, or triggering further workflows based on task status.

Practical examples include:

  • Automatically retrieving pending or completed tasks for an agent to update dashboards.
  • Triggering notifications or follow-up actions when certain tasks are assigned or completed.
  • Aggregating task data across multiple agents for centralized management.

Properties

Name Meaning
Agent ID The unique identifier of the agent from which to retrieve tasks.
Limit The maximum number of task results to return. Must be at least 1. Defaults to 50.

Output

The node outputs JSON data containing the list of tasks retrieved for the specified agent. Each item in the output corresponds to a task object as returned by the Tactical RMM API. The structure typically includes details such as task ID, description, status, timestamps, and other relevant metadata.

If the node supports binary data output (not indicated here), it would represent attachments or files related to tasks, but this is not evident from the provided code.

Dependencies

  • Requires an active connection to the Tactical RMM API.
  • Needs an API authentication token or key configured in n8n credentials to authorize requests.
  • The node depends on internal action modules for agents, clients, alerts, and software, and uses a router method to dispatch operations.

Troubleshooting

  • Common issues:
    • Invalid or missing Agent ID will cause the API call to fail or return no data.
    • Exceeding API rate limits may result in errors or throttling.
    • Network connectivity problems can prevent successful API communication.
  • Error messages:
    • Authentication errors indicate invalid or missing API credentials; verify and update the API key.
    • "Resource not found" or similar errors suggest the Agent ID does not exist; confirm the correct ID.
    • Validation errors on the "Limit" property if set below 1; ensure the limit is a positive integer.

Links and References

Discussion