Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
Queries → Get Device Health Report
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve a device health report based on specified filters and pagination options. It is useful for IT administrators or support teams who want to monitor the health status of devices managed within NinjaOne, enabling them to filter devices by specific criteria and handle large result sets through pagination.
Practical examples include:
- Fetching all devices with a particular health status (e.g., "healthy", "warning", "critical").
- Filtering devices by a custom device filter string.
- Paginating through large lists of device health reports using cursor and page size parameters.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: a string used to filter devices according to custom criteria. |
| Health | Health status filter: a string specifying the desired health status of devices to fetch. |
| Cursor | Cursor name: a string used for pagination to indicate the position in the result set. |
| Page Size | Limit number of records per page: a number defining how many records to return per page. |
Output
The node outputs JSON data representing the device health report retrieved from the NinjaOne API. The structure corresponds to the API response for device health queries, typically including details about each device's health status and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API via an OAuth2 API credential.
- The node uses the NinjaOne API endpoint
/v2/queries/device-health-report(inferred from context) with HTTP GET method. - Proper API authentication credentials must be configured in n8n for successful requests.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid filter values may result in empty responses or API errors.
- Pagination parameters (cursor, pageSize) must be correctly managed to avoid missing or duplicate data.
Error messages:
- Errors returned from the NinjaOne API will be surfaced as error messages in the node output.
- If no binary data is found when expected (not applicable here), an error would be thrown.
- Network or permission errors should be checked by verifying API key validity and network connectivity.
Links and References
- NinjaOne API Documentation (general reference for API endpoints and parameters)
- n8n OAuth2 Credential Setup (for configuring API authentication)