Actions53
- Account Actions
- Device Actions
- Site Actions
- Alert Actions
- Job Actions
- Audit Actions
- System Actions
- Filter Actions
Overview
The node interacts with the Datto RMM API to retrieve historical execution data for a specific job. It allows users to fetch the job's history records, optionally filtered by date range and status, and supports pagination or retrieving all results automatically. This is useful for monitoring job executions, auditing past runs, troubleshooting failures, or analyzing job performance over time.
Practical examples include:
- Fetching all history entries of a backup job within the last month to verify successful completions.
- Retrieving only failed job runs to investigate recurring issues.
- Paginating through large job histories when dealing with extensive logs.
Properties
| Name | Meaning |
|---|---|
| Job | Select the specific job from the list of available jobs to retrieve history for. |
| Retrieve All | Whether to automatically retrieve all history entries using pagination (true), or manually specify page and max results (false). |
| Page | The page number to retrieve when not retrieving all results automatically (1-based). |
| Max Results | Maximum number of history entries to return per page when manual pagination is used. |
| Start Date | Filter to include only job history entries starting from this date/time (ISO 8601 format). |
| End Date | Filter to include only job history entries up to this date/time (ISO 8601 format). |
| Status Filter | Filter job history entries by their execution status. Options: All, Completed, Failed, Running, Queued. |
| Fields to Include | Select which fields to include in the response for each job history entry. |
Output
The node outputs JSON data containing an array of job history entries matching the specified filters. Each entry includes fields such as timestamps, status, and other job-specific details depending on the selected fields. This structured output can be used downstream for reporting, alerting, or further processing.
The node does not output binary data.
Dependencies
- Requires an active connection to the Datto RMM API via an API key credential configured in n8n.
- The node depends on the Datto RMM API endpoints for jobs and job history.
- Pagination support relies on the API's ability to return paged results.
Troubleshooting
Common Issues:
- Invalid or expired API credentials will cause authentication errors.
- Selecting a job that no longer exists or is inaccessible may result in empty or error responses.
- Incorrect date formats for start/end date filters can lead to request failures.
- Requesting too many results per page might hit API limits or timeouts.
Error Messages:
- Authentication errors: Verify the API key credential and its permissions.
- "Resource job is not supported": Ensure the resource and operation are correctly set to "job" and "getHistory".
- Pagination errors: When manual pagination is used, ensure page and max results are positive integers.