Actions120
- Alert Actions
- Backup Actions
- Custom Field Actions
- Device Actions
- Document Template Actions
- Group Actions
- Knowledge Base Article Actions
- Location Actions
- Organization Actions
- Organization Document Actions
- Query Actions
- Alerts
- Antivirus Status
- Antivirus Threats
- Backup Usage
- Computer Systems
- Custom Fields
- Custom Fields (Detailed)
- Device Health
- Disks
- Logged-On Users
- Network Interfaces
- Operating Systems
- OS Patch Installs
- OS Patches
- Policy Overrides
- Processors
- RAID Controllers
- RAID Drives
- Scoped Custom Fields
- Scoped Custom Fields (Detailed)
- Software
- Software Patch Installs
- Software Patches
- Volumes
- Windows Services
- Related Item Actions
- Software License Actions
- System Actions
- Get Activities
- Get Contacts
- Get Device Custom Fields
- Get Device Roles
- Get Devices (Detailed)
- Get End Users
- Get Jobs
- Get Locations
- Get Notification Channels
- Get Notification Channels (Enabled)
- Get Organizations (Detailed)
- Get Policies
- Get Scheduled Tasks
- Get Scripting Languages
- Get Scripts
- Get Software Products
- Get Technicians
- Get User Roles
- Ticketing Actions
- User Actions
- Webhook Actions
Query → Operating Systems
AI-generatedSummary
Retrieve operating-system records from NinjaOne’s query endpoint. Use the optional filters to limit results by pagination, monitoring timestamp, approval status, device classes, device, location, online status, organization, or role.
Inputs
- Authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials and provide the matching NinjaOne credentials.
- Filters — Optional query parameters: Cursor for pagination, Page Size (default 200), and Timestamp. Device filters include Approval Status, Device Classes, Device ID, Location ID, Online Status, Organization ID, and Role ID. ID fields accept comma-separated values.
Output shape
A list of operating-system records, with each record returned as a separate n8n item.
The node sends a GET request to NinjaOne’s operating-systems query endpoint. It passes non-empty filter values as query parameters and combines structured device filters into NinjaOne’s device-filter expression. This operation makes one request; it does not automatically fetch subsequent pages.