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 Operating Systems
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about operating systems via a query operation. Specifically, the "Get Operating Systems" operation under the "Queries" resource allows users to fetch paginated lists of operating system data filtered by device, timestamp, and cursor position. This is useful for IT administrators or automation workflows that need to monitor or report on the operating systems present in their managed environment.
Practical examples include:
- Fetching all operating systems currently reported by devices.
- Filtering operating systems by a specific device identifier.
- Paginating through large sets of operating system records using cursors and page size limits.
- Retrieving operating system data as of a particular monitoring timestamp.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: Filter results by a specific device identifier (string). |
| Ts | Monitoring timestamp filter: Filter results based on a specific monitoring timestamp (string). |
| Cursor | Cursor name: Used for pagination to specify the starting point for the next set of results (string). |
| Page Size | Limit number of records per page: Controls how many operating system records are returned per request (number). |
Output
The node outputs JSON data representing the response from the NinjaOne API for the requested operating systems query. The structure typically includes an array of operating system records along with pagination metadata such as cursors if applicable.
If binary data were involved, it would be summarized here; however, this operation deals only with JSON data.
Dependencies
- Requires an active connection to the NinjaOne API authenticated via an OAuth2 API key credential.
- The node uses the NinjaOne API endpoints under
/v2/queriesor similar paths (inferred from context). - No additional external dependencies beyond the NinjaOne API and n8n's HTTP request helper.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing invalid filter values (e.g., malformed timestamps or unknown device IDs) may result in empty responses or API errors.
- Pagination parameters like cursor and page size must be used correctly to avoid missing data or infinite loops.
Error messages:
- Errors from the NinjaOne API will be returned in the JSON output under an
errorfield if "Continue On Fail" is enabled. - If binary data is expected but missing (not relevant here), the node throws an error indicating missing binary data.
- Network or authentication errors will throw exceptions stopping execution unless "Continue On Fail" is enabled.
- Errors from the NinjaOne API will be returned in the JSON output under an
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes
- OAuth2 Authentication setup in n8n (for connecting to NinjaOne API)
Note: The summary is based solely on static analysis of the provided source code and property definitions without runtime behavior inference.