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 OS Patch Scan
AI-generatedOverview
This node integrates with the NinjaOne API to perform various management-related operations. Specifically, for the "Management" resource and the "Submit OS Patch Scan" operation, it submits a request to initiate an operating system patch scan on a specified device. This is useful in IT management scenarios where automated patch compliance and vulnerability scanning are required to maintain security and system health.
Practical examples include:
- Automatically triggering patch scans on devices after deployment or at scheduled intervals.
- Integrating patch scan submissions into broader automation workflows for IT asset management.
- Ensuring devices are up-to-date by programmatically initiating scans and then acting on the results.
Properties
| Name | Meaning |
|---|---|
| Id | Device identifier (number). The unique ID of the device on which to submit the OS patch scan. |
Output
The node outputs JSON data representing the response from the NinjaOne API after submitting the OS patch scan request. The exact structure depends on the API response but typically includes confirmation details about the scan submission status.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests to the NinjaOne API.
- The node uses the NinjaOne OAuth2 API credential for secure access.
- Network connectivity to the NinjaOne API endpoint is necessary.
Troubleshooting
Common issues:
- Missing or invalid device ID: Ensure the "Id" property is set correctly and corresponds to a valid device in NinjaOne.
- Authentication errors: Verify that the API credentials are properly configured and have sufficient permissions.
- Network or API downtime: Check network connectivity and NinjaOne service status.
Error messages:
"No binary data exists on item!"or"No binary data property ... does not exist on item!"— These do not apply to this operation but may appear if other operations expecting binary input are used incorrectly.- API error responses will be returned as JSON with an
errorfield if the node is set to continue on failure.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation for configuring credentials and using HTTP request nodes