Actions22
- Agent Actions
- Alert Actions
- Client Actions
- Software Actions
Overview
The node integrates with the Tactical RMM API to perform bulk actions on agents. It allows users to execute commands such as rebooting, shutting down, updating, or pinging multiple agents simultaneously. This is particularly useful in IT management scenarios where administrators need to manage a fleet of machines efficiently without interacting with each agent individually.
Practical examples include:
- Rebooting all agents that have pending updates.
- Scheduling shutdowns for maintenance windows.
- Pinging agents to check their availability status.
- Triggering updates on multiple agents at once.
Properties
| Name | Meaning |
|---|---|
| Agent IDs | Comma-separated list of agent IDs to perform the bulk action on. |
| Action | The bulk action to perform on the agents. Options: Reboot, Shutdown, Update Agent, Ping. |
| Mode | When to execute the bulk action. Options: Now (immediate execution), Schedule (deferred). |
Output
The node outputs JSON data representing the result of the bulk action performed on the specified agents. This typically includes success or failure statuses for each agent involved in the operation. The output does not handle binary data.
Dependencies
- Requires an API key credential for authenticating with the Tactical RMM API.
- The node depends on the Tactical RMM service being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
- Common issues:
- Invalid or missing agent IDs can cause the bulk action to fail.
- Incorrect API credentials will prevent successful communication with the Tactical RMM API.
- Network connectivity problems may lead to timeouts or unreachable errors.
- Error messages:
- Authentication errors indicate invalid or expired API keys; verify and update credentials.
- Validation errors related to agent IDs suggest formatting issues; ensure IDs are comma-separated strings.
- Scheduling errors may occur if the "Schedule" mode is selected but no scheduling details are provided; confirm scheduling parameters if applicable.