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 → Volumes
AI-generatedSummary
Query NinjaOne for volume/storage records across devices, optionally filtering the results. The operation sends one GET request to the volumes query endpoint for each input item and returns the response as n8n output items.
Inputs
- Authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials and configure the matching NinjaOne credentials.
- Filters — Optional query parameters: Cursor for pagination, Include for additional response data, Page Size (default 200), and Timestamp for monitoring data. You can also filter by approval status, device classes, device IDs, location IDs, online status, organization IDs, or role IDs. Multiple IDs are comma-separated; selected device filters are combined into a NinjaOne device filter expression.
Output shape
One n8n item per record when the API response is an array; otherwise, one item containing the response object.
Calls GET /api/v2/queries/volumes. The node passes the selected filters as query parameters, combining device filters into df. It does not fetch additional pages automatically for this operation; use Cursor and Page Size for pagination.
Examples
Example 1: Get volume information for online Windows workstations in organization 5.
Select Client Credentials authentication. Set Device Classes to WINDOWS_WORKSTATION, Online Status to Online, and Organization ID to 5.
Example 2: Request the next page of volume records with additional response data.
Set Cursor to the pagination cursor and Page Size to the desired number of records; optionally set Include and Timestamp.
