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 Pending Failed Rejected OS Patches
AI-generatedOverview
This node operation retrieves information about pending, failed, or rejected operating system patches for a specific device managed in NinjaOne. It is useful for IT administrators and support teams who want to monitor patch compliance and troubleshoot patch deployment issues on individual devices.
Typical use cases include:
- Checking which OS patches are pending installation on a device.
- Identifying failed or rejected patches to investigate patching problems.
- Filtering patches by status, type, or severity to prioritize remediation efforts.
For example, an admin could use this node to get all critical security patches that failed on a particular workstation to quickly address vulnerabilities.
Properties
| Name | Meaning |
|---|---|
| Id | Device identifier (number). The unique ID of the device for which to retrieve patches. |
| Status | Patch status filter. Possible values depend on API but typically include "pending", "failed", "rejected". Filters patches by their current status. |
| Type | Patch type filter. Filters patches by their type, e.g., security, feature update, etc. |
| Severity | Patch severity filter. Filters patches by severity level, such as critical, important, moderate, etc. |
Output
The output is a JSON array where each item contains details about OS patches matching the specified filters for the given device. Each patch object typically includes fields such as patch ID, name, status, type, severity, and other metadata returned by the NinjaOne API.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on the NinjaOne API endpoint
/v1/devices/{id}/patches(implied from context) with query parameters for filtering. - Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
- Missing or invalid device ID: Ensure the
Idproperty is set correctly and corresponds to an existing device in NinjaOne. - Empty results: If no patches are returned, verify that the device has patches matching the specified filters (
Status,Type,Severity). Try removing filters to broaden the search. - Authentication errors: Confirm that the NinjaOne API credentials are valid and have sufficient permissions.
- API rate limits or downtime: Temporary failures may occur if the NinjaOne API is unavailable or rate-limited; retry after some time.
Links and References
- NinjaOne API Documentation (general reference for endpoints and patch-related resources)
- n8n OAuth2 Credential Setup (for configuring NinjaOne API credentials)