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 Software Patches
AI-generatedOverview
This node operation retrieves software patches for a specific device that are in one of the following states: pending, failed, or rejected. It allows filtering these patches by various criteria such as status, product identifier, type, and impact. This is useful for IT administrators or support teams who want to monitor and manage patch compliance and issues on devices managed through NinjaOne.
Practical examples include:
- Fetching all failed patches on a device to troubleshoot update problems.
- Listing pending patches filtered by patch type to prioritize deployment.
- Reviewing rejected patches with a specific impact level to assess risk.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which to retrieve patch information (required). |
| Status | Filter patches by their status (e.g., pending, failed, rejected). |
| Product Identifier | Filter patches by the product identifier associated with the patch. |
| Type | Filter patches by the type of patch (e.g., security, feature update). |
| Impact | Filter patches by their impact level (e.g., critical, moderate, low). |
Output
The output is an array of JSON objects where each object represents a software patch matching the specified filters for the given device. Each JSON object contains details about the patch such as its status, product identifier, type, impact, and other relevant metadata returned by the NinjaOne API.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on the NinjaOne API endpoint
/v2/devices/{id}/patches(implied from context) to fetch patch data. - Proper configuration of the NinjaOne OAuth2 API credentials within n8n is necessary.
Troubleshooting
- Missing or invalid device Id: The
Idproperty is required. Ensure it is provided and corresponds to a valid device in NinjaOne. - API authentication errors: Verify that the OAuth2 credentials are correctly configured and have sufficient permissions.
- Empty results: If no patches are returned, check filter values; overly restrictive filters may exclude all patches.
- Network or API errors: These will be surfaced as error messages. Check network connectivity and NinjaOne service status.
Links and References
- NinjaOne API Documentation (general reference for endpoints and patch data)
- n8n OAuth2 Credential Setup (for configuring NinjaOne OAuth2 credentials)