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 Scan
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 Scan" operation, it submits a request to initiate or report a software patch scan on a specified device identified by its ID.
Common scenarios where this node is beneficial include:
- Automating patch management workflows by triggering patch scans on devices.
- Integrating patch status checks into broader IT automation pipelines.
- Ensuring devices are up-to-date by programmatically submitting patch scan requests.
For example, an IT administrator could use this node in an n8n workflow to automatically submit patch scans for devices that have reported issues or after deploying new software.
Properties
| Name | Meaning |
|---|---|
| Id | Device identifier (number). The unique ID of the device on which to submit the software patch scan. |
Output
The node outputs JSON data representing the response from the NinjaOne API after submitting the software patch scan request. This typically includes details about the scan submission status or any relevant metadata returned by the API.
No binary data output is indicated for this operation.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for the NinjaOne API.
- The node depends on the NinjaOne API being accessible and the user having appropriate permissions to submit patch scans.
- No additional external services or environment variables are explicitly required beyond the API credential.
Troubleshooting
Common Issues:
- Missing or invalid device ID: Ensure the "Id" property is provided and corresponds to a valid device in NinjaOne.
- Authentication errors: Verify that the OAuth2 credentials are correctly set up and have not expired.
- Network or API availability issues: Confirm that the NinjaOne API endpoint is reachable.
Error Messages:
"No binary data exists on item!"or"No binary data property ... does not exist on item!"— These errors relate to other operations involving binary data upload and do not apply to this operation.- API error messages returned in the JSON response will be passed through; check the message for details such as permission denied or invalid parameters.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation for setting up OAuth2 credentials and using HTTP Request nodes
Note: The provided bundled source code implements multiple resources and operations. The summary above focuses solely on the "Management" resource and "Submit Software Patch Scan" operation as requested.