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 Installed OS Patches
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about installed operating system patches on devices. It allows users to query installed OS patches with various filters such as device, patch status, installation date ranges, and pagination controls. This is useful for IT administrators or security teams who want to monitor patch compliance, identify failed patch installations, or generate reports on patch deployment status across their managed devices.
Practical examples include:
- Fetching all patches installed before a certain date to audit historical patching.
- Filtering patches by status (e.g., only failed patches) to troubleshoot update issues.
- Paginating through large sets of patch data using cursor and page size parameters.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: specify a device identifier or name to limit patches to that device |
| Status | Patch status filter: choose between FAILED or INSTALLED to filter patches by status |
| Installed Before | Include patches installed before the specified date (date string expected) |
| Installed After | Include patches installed after the specified date (date string expected) |
| Cursor | Cursor name for pagination to continue from a previous result set |
| Page Size | Limit number of records returned per page (number) |
Output
The node outputs JSON data representing the response from the NinjaOne API for the installed OS patches query. The structure typically includes details about each patch such as patch identifiers, installation dates, status, and associated device information.
If binary data were involved (not in this operation), it would be included separately, but this operation deals solely with JSON data.
Dependencies
- Requires an active connection to the NinjaOne API via an OAuth2 API credential.
- The node uses the NinjaOne API endpoints under
/v2/queries/...(implied by routing). - Proper API authentication credentials must be configured in n8n for the node to function.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect date formats for "Installed Before" or "Installed After" may lead to API errors or empty results.
- Using an invalid cursor or page size might result in pagination errors or unexpected responses.
- If no patches match the filters, the output will be empty; verify filter values.
Error messages:
- Authentication errors: Ensure the OAuth2 API key is valid and has required permissions.
- Validation errors from the API: Check that date strings are correctly formatted (ISO 8601 recommended).
- Network or timeout errors: Verify network connectivity and NinjaOne API availability.
Links and References
- NinjaOne API Documentation (general): https://docs.ninjaone.com/api/
- NinjaOne Patch Management API section (for detailed query parameters and response schema)
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
Note: The summary is based on static analysis of the provided source code and property definitions without runtime execution.