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 → Custom Fields (Detailed)
AI-generatedSummary
Query detailed custom field data from NinjaOne devices with optional pagination, field selection, update-date, and device filters. Choose OAuth2 or client credentials authentication; the operation makes a GET request and does not modify data.
Inputs
- Authentication (required) — Select OAuth2 (Authorization Code) or Client Credentials and provide the corresponding credentials.
- Filters — Optional query filters: Cursor for pagination, comma-separated Fields to return, Page Size (default 200), Updated After date, Approval Status, Device Classes, comma-separated Device ID, Location ID, Organization ID, or Role ID values, and Online Status. Device filters are combined into NinjaOne's device-filter expression.
Output shape
A list of n8n items, one per returned record; each record is in the item's JSON.
The response is taken directly from NinjaOne's detailed custom fields query endpoint. A non-array response is emitted as a single item. The operation passes the cursor and page size as query parameters but does not automatically fetch further pages.