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
Devices → Get Device Software
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve software information installed on a specific device. It is designed to fetch detailed software data for devices managed within the NinjaOne platform. This functionality is useful in IT asset management, software inventory tracking, and compliance auditing scenarios where knowing the exact software installed on devices is critical.
For example, an IT administrator can use this node to automatically gather software details from all company devices to ensure licensing compliance or to identify outdated software versions that require updates.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device whose software information you want to retrieve. |
Output
The node outputs JSON data containing the software details of the specified device as returned by the NinjaOne API. The structure typically includes software names, versions, installation dates, and other relevant metadata about each software item installed on the device.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API.
- Requires an API authentication token configured via OAuth2 credentials in n8n.
- The node uses the NinjaOne OAuth2 API credential to authenticate requests.
Troubleshooting
Common issues:
- Invalid or missing device ID: Ensure the device ID provided exists and is correct.
- Authentication errors: Verify that the OAuth2 credentials are correctly set up and have sufficient permissions.
- Network or API downtime: Check network connectivity and NinjaOne service status.
Error messages:
"No binary data exists on item!"or similar will not occur here since this operation does not handle binary data.- API errors returned from NinjaOne (e.g., 404 Not Found if device ID is invalid) will be surfaced; verify the device ID and API access rights.
If the node is set to continue on failure, errors will be included in the output JSON under an error field.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and data structures)
- n8n OAuth2 Credentials Setup