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 Pending Failed Rejected Software Patches
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve data related to software patches that are pending, failed, or rejected. Specifically, for the "Queries" resource and the "Get Pending Failed Rejected Software Patches" operation, it fetches filtered lists of software patches based on various criteria such as device filters, patch status, type, impact, and pagination controls.
This node is beneficial in IT management and security automation workflows where monitoring and managing software patch statuses across devices is critical. For example, an IT administrator can use this node to automatically gather all failed or rejected patches to trigger alerts or remediation processes.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: Filter patches by specific device identifiers or criteria. |
| Ts | Monitoring timestamp filter: Filter patches based on a specific monitoring timestamp. |
| Status | Patch Status filter: Filter patches by their status (e.g., pending, failed, rejected). |
| Product Identifier | Product Identifier: Filter patches by product identifier. |
| Type | Patch Type filter: Filter patches by the type of patch. |
| Impact | Patch Impact filter: Filter patches by the impact level of the patch. |
| Cursor | Cursor name: Used for pagination to specify the cursor position in the result set. |
| Page Size | Limit number of records per page: Controls how many patch records are returned per page. |
Output
The node outputs JSON data representing the response from the NinjaOne API for the requested query. The structure of the JSON output corresponds to the list of software patches matching the applied filters, including details about each patch's status, type, impact, associated devices, and other metadata.
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
/v2/queries/pending-failed-rejected-software-patches(implied by the operation context). - Proper configuration of the NinjaOne OAuth2 API credentials within n8n is necessary.
Troubleshooting
Common Issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect filter values may result in empty responses or errors.
- Pagination parameters (
cursor,pageSize) must be used correctly to navigate large datasets.
Error Messages:
- Errors returned from the NinjaOne API will be included in the node output if "Continue On Fail" is enabled.
- Typical errors include authorization errors, invalid parameter errors, or network issues.
Resolution Tips:
- Verify that the OAuth2 credentials are correctly configured and valid.
- Double-check filter values for correctness and supported formats.
- Use pagination parameters carefully to avoid missing data or infinite loops.
Links and References
- NinjaOne API Documentation (general reference for API endpoints and parameters)
- n8n OAuth2 Credential Setup (for configuring OAuth2 credentials in n8n)