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
Management → Submit Software Patch Apply
AI-generatedOverview
This node integrates with the NinjaOne API to perform various management-related operations. Specifically, for the "Management" resource and the "Submit Software Patch Apply" operation, it allows users to submit a request to apply a software patch to a device identified by its ID. This is useful in IT management scenarios where automated patch deployment and tracking are required to maintain system security and compliance.
Practical examples include:
- Automatically triggering patch application on devices after a vulnerability scan.
- Integrating patch management into broader IT workflows to ensure devices stay updated without manual intervention.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device on which the software patch should be applied. This is a required numeric value. |
Output
The node outputs JSON data representing the response from the NinjaOne API after submitting the software patch apply request. The structure typically includes details about the submission status or any relevant metadata returned by the API.
If the node supports binary data output (not indicated for this operation), it would represent files or attachments related to the operation, but for this specific operation, only JSON output is expected.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on the NinjaOne API being accessible and the user having appropriate permissions to submit patch apply requests.
- Configuration of the OAuth2 credential within n8n is necessary before using this node.
Troubleshooting
Common issues:
- Invalid or missing device ID: Ensure the "Id" property is correctly set and corresponds to a valid device in NinjaOne.
- Authentication errors: Verify that the OAuth2 credentials are correctly configured and have not expired.
- API connectivity problems: Check network access to the NinjaOne API endpoint.
Error messages:
"No binary data exists on item!"or"No binary data property ... does not exist on item!"— These errors relate to other operations expecting binary input and do not apply to this operation.- General API errors will be returned in the JSON output under an error field if "Continue On Fail" is enabled; otherwise, they will cause the node to fail execution.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring OAuth2 authentication)