Actions53
- Account Actions
- Device Actions
- Site Actions
- Alert Actions
- Job Actions
- Audit Actions
- System Actions
- Filter Actions
Overview
This node enables running a job on all devices within a selected site in Datto RMM. It is designed to execute a specified component or script across multiple devices simultaneously, with optional filtering and execution controls. This is particularly useful for administrators who want to deploy updates, run maintenance scripts, or perform audits on an entire site or a subset of devices without manually targeting each device.
Practical examples:
- Running a security patch deployment script on all Windows servers in a specific site.
- Executing a diagnostic component on all online laptops at a location.
- Performing batch configuration changes on workstations filtered by operating system.
Properties
| Name | Meaning |
|---|---|
| Site | Select the site where the job should be executed on all devices. |
| Component | Select the component or script to execute on all devices in the chosen site. |
| Job Name | Name assigned to this job execution; applied uniformly to all targeted devices. |
| Device Filters | Optional filters to narrow down devices for job execution: |
| - Operating System | Filter devices by their operating system (e.g., Windows, Linux). |
| - Device Type | Filter devices by type: All, Workstation, Server, Laptop. |
| - Online Only | If true, only devices currently online will have the job executed. |
| Execution Options | Controls for how the job runs: |
| - Batch Size | Number of devices processed per batch (1 to 50, recommended 10-25). |
| - Continue on Device Failure | Whether to continue executing on other devices if one device fails. |
| - Include Offline Devices in Results | Whether to include skipped devices (offline or filtered out) in the final results. |
Output
The node outputs JSON data summarizing the job execution results. This includes information about which devices the job was run on, success or failure status per device, and optionally details about devices that were skipped due to being offline or filtered out. The output helps track the overall execution status and troubleshoot any device-specific issues.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Datto RMM API.
- Needs proper configuration of the base API URL in the node credentials.
- Relies on Datto RMM API endpoints for sites, components, and job execution.
- Uses dynamic loading of options for sites and components via API calls.
Troubleshooting
Common Issues:
- Invalid or missing API credentials will cause authentication failures.
- Selecting a site or component that does not exist or has no devices may result in empty execution or errors.
- Network connectivity issues can prevent API calls from succeeding.
- Setting batch size too high might cause timeouts or performance degradation.
Error Messages:
- "Resource job is not supported yet" — indicates an unsupported resource selection; ensure "job" resource is selected.
- API errors related to permissions or invalid parameters — verify API key permissions and input values.
- Device filter misconfiguration leading to zero devices found — adjust filters or disable them to include more devices.
Resolutions:
- Verify and update API credentials.
- Confirm site and component UIDs are valid and accessible.
- Adjust device filters to match available devices.
- Reduce batch size if encountering timeouts.