Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node operation retrieves the list of pending, failed, or rejected operating system patches for a specific device. It is useful in IT management and security scenarios where administrators need to monitor patch compliance and identify devices that require attention due to uninstalled or problematic OS patches. For example, an IT admin can use this node to fetch all critical patches that have failed on a particular device to prioritize remediation efforts.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which to retrieve OS patch information. |
| Additional Query Parameters | Optional filters to refine the patch results: |
| - Status | Filter patches by their status (e.g., pending, failed, rejected). |
| - Type | Filter patches by type (e.g., security, feature update). |
| - Severity | Filter patches by severity level (e.g., critical, important). |
Output
The node outputs JSON data containing details about the OS patches matching the specified criteria for the given device. This typically includes patch metadata such as patch ID, name, status, type, severity, and other relevant attributes. The output does not include binary data.
Dependencies
- Requires an API key credential for authenticating with the external service.
- Needs the base URL of the API configured in the node credentials.
- Depends on the external AvantGuard NinjaOne API to fetch device patch information.
Troubleshooting
Common issues:
- Invalid or missing device ID will result in no data or errors.
- Incorrect API credentials or base URL configuration will cause authentication failures.
- Using unsupported filter values in additional query parameters may return empty results or errors.
Error messages:
- Authentication errors indicate invalid or expired API keys; verify and update credentials.
- "Device not found" errors suggest the provided device ID does not exist; confirm the ID.
- Query parameter validation errors mean the filters used are not recognized; check allowed values.
Links and References
- AvantGuard NinjaOne API Documentation (example link, replace with actual)
- n8n documentation on creating custom nodes