Actions22
- Agent Actions
- Alert Actions
- Client Actions
- Software Actions
Overview
This node integrates with the Tactical RMM API to retrieve data related to various resources, including clients. Specifically, the "Get Many" operation for the Client resource fetches multiple client records from the Tactical RMM system. This is useful in scenarios where you need to list or process multiple clients at once, such as generating reports, syncing client data with other systems, or performing bulk operations.
For example, you might use this node to:
- Retrieve a list of all clients managed in Tactical RMM.
- Limit the number of clients fetched to avoid overwhelming downstream processes.
- Use the client data to trigger further automation workflows based on client attributes.
Properties
| Name | Meaning |
|---|---|
| Limit | Max number of client results to return. |
The "Limit" property controls how many client records the node will fetch in one execution. It must be a number greater than or equal to 1, with a default value of 50.
Output
The node outputs JSON data containing an array of client objects retrieved from the Tactical RMM API. Each object represents a client with its associated properties as defined by the API response.
If the node supports binary data output (not indicated here), it would typically represent attachments or files related to clients, but this is not evident from the provided code.
Dependencies
- Requires an API key credential for authenticating with the Tactical RMM API.
- The node expects the Tactical RMM API to be accessible and properly configured.
- No additional external dependencies are indicated beyond the API connection.
Troubleshooting
Common issues:
- Authentication failures due to missing or invalid API credentials.
- Network connectivity problems preventing access to the Tactical RMM API.
- Exceeding API rate limits if requesting too many clients at once.
Error messages:
- Errors related to authentication usually indicate incorrect or missing API keys; verify and update credentials.
- Timeout or network errors suggest checking internet connectivity or API endpoint availability.
- If the limit parameter is set below 1, the node may throw validation errors; ensure the limit is a positive integer.
Links and References
- Tactical RMM Official Documentation
- Tactical RMM API Reference (for details on client data structure and endpoints)