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 → Scoped Custom Fields
AI-generatedSummary
Query NinjaOne’s scoped custom field records with the GET /api/v2/queries/scoped-custom-fields endpoint. Configure optional filters to select fields, pagination, update date, and matching devices; results are returned as n8n items.
Inputs
- Authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials and configure the matching NinjaOne credentials.
- Filters — Optional query parameters: Cursor for pagination, Fields as a comma-separated list of custom field names, Page Size (default 200), and Updated After date. Device filters can also limit results by approval status, device classes, device IDs, location IDs, online status, organization IDs, or role IDs. ID filters accept comma-separated values.
Output shape
A list of n8n items, each containing a returned record in json.
The operation makes one API request using the configured cursor and page size; it does not automatically fetch subsequent pages. Device filters are combined into NinjaOne’s
dfexpression, while other nonempty filters are sent as query parameters.