Actions53
- Account Actions
- Device Actions
- Site Actions
- Alert Actions
- Job Actions
- Audit Actions
- System Actions
- Filter Actions
Overview
This node interacts with the Datto RMM API to retrieve information about jobs and their outputs on managed devices. Specifically, the "Job" resource with the "Get Standard Output" operation fetches the standard output (stdout) generated by a particular job executed on a specified device.
Use cases include:
- Retrieving logs or output from automated tasks or scripts run via Datto RMM jobs.
- Monitoring job execution results for troubleshooting or auditing purposes.
- Integrating job output data into workflows for further processing or alerting.
For example, after running a patch deployment job on multiple devices, you can use this node to collect the stdout from each device to verify success or diagnose issues.
Properties
| Name | Meaning |
|---|---|
| Job | Select the specific job whose standard output you want to retrieve. Options are loaded dynamically from available jobs. |
| Device | Select the device on which the job was run to get its standard output. Options are loaded dynamically from available devices. |
Output
The node outputs JSON data containing the standard output text of the selected job as executed on the specified device. The exact structure depends on the API response but typically includes fields such as:
jobUid: Identifier of the job.deviceUid: Identifier of the device.stdOut: The standard output content (text) produced by the job on that device.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Datto RMM API using an API key credential configured in n8n.
- The node dynamically loads options for jobs and devices by querying the Datto RMM API endpoints.
- Proper permissions on the API key are necessary to access job and device information and retrieve job outputs.
Troubleshooting
Common Issues:
- No jobs or devices appear in the dropdown lists: This usually indicates connectivity issues or insufficient API permissions.
- Empty or missing standard output: The job may not have produced any output, or the job/device combination is invalid.
- API errors due to expired or invalid credentials.
Error Messages:
- Errors related to resource or operation not supported indicate misconfiguration of the resource/operation parameters.
- Network or authentication errors suggest checking API URL, credentials, and network connectivity.
Resolutions:
- Verify API credentials and permissions.
- Confirm the job has completed and generated output.
- Ensure the device selected actually ran the job.