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
Devices → Get Device Installed OS Patches
AI-generatedOverview
This node operation retrieves the list of installed operating system patches on a specific device managed by NinjaOne. It allows filtering patches based on their installation status and installation date ranges. This is useful for IT administrators who want to audit patch compliance, verify security updates, or troubleshoot patch-related issues on devices.
Practical examples:
- Fetch all installed patches on a device to verify it meets security standards.
- Retrieve only failed patches to identify update problems.
- List patches installed within a certain timeframe to track recent changes.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which to retrieve installed OS patches. |
| Status | Filter patches by their status; options include FAILED or INSTALLED. |
| Installed Before | Include only patches installed before the specified date (date string). |
| Installed After | Include only patches installed after the specified date (date string). |
Output
The output is an array of JSON objects where each object represents the response from the NinjaOne API containing details about the installed OS patches on the specified device. The exact structure depends on the API response but typically includes patch identifiers, names, statuses, installation dates, and other metadata related to each patch.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node expects the NinjaOne API credentials to be configured in n8n.
- Network access to the NinjaOne service endpoint is necessary.
Troubleshooting
- Missing or invalid device Id: Ensure the device identifier is correct and exists in NinjaOne.
- Authentication errors: Verify that the OAuth2 credentials are valid and have not expired.
- Empty results: Check filter parameters such as status and date ranges; overly restrictive filters may return no data.
- API request failures: Network issues or NinjaOne service outages can cause errors; retry later or check service status.
- Invalid date formats: Dates for "Installed Before" and "Installed After" must be valid date strings recognizable by the API.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and patch data schema)
- n8n OAuth2 Credential Setup