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 Custom Fields Detailed Report
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve a detailed report of custom fields related to queries. It is designed to fetch paginated data about custom fields, optionally filtered by device, update date, and other parameters. This node is useful for IT administrators or automation engineers who want to programmatically access detailed metadata about custom fields in their NinjaOne environment, such as for auditing, reporting, or integration with other systems.
Practical examples include:
- Retrieving all custom fields updated after a certain date to sync with an external database.
- Fetching a limited number of records per page to process large datasets incrementally.
- Filtering results by device or specific fields to focus on relevant data subsets.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: filter the query results by a specific device identifier or name. |
| Cursor | Cursor name: used for pagination to continue fetching results from where the last request ended. |
| Page Size | Limit number of records per page: controls how many records are returned in one API call. |
| Updated After | Custom fields updated after specified date: filters results to only those updated after this date. |
| Fields | Comma-separated list of fields: specify which fields to include in the response. |
| Show Secure Values | Flag indicating if secure values should be returned as plain text without encryption (true/false). |
Output
The node outputs JSON data representing the detailed report of custom fields retrieved from the NinjaOne API. The structure corresponds directly to the API response and includes the requested fields, pagination cursors, and any metadata provided by the API.
If the API returns binary data (not indicated for this operation), it would be included accordingly, but for this operation, output is purely JSON.
Dependencies
- Requires an active connection to the NinjaOne API using OAuth2 authentication.
- The node depends on the NinjaOne API endpoint
/v2/queries/custom-fields-detailed-report(inferred from context). - Proper API credentials must be configured in n8n to authenticate requests.
Troubleshooting
- Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Incorrect property values (e.g., invalid date format for "Updated After") may result in API errors.
- Pagination issues if the cursor is not managed correctly could lead to repeated or missed data.
- Error messages:
- Errors from the API will be returned in the node's output if "Continue On Fail" is enabled.
- Typical errors include unauthorized access, invalid parameters, or rate limiting.
- Resolutions:
- Verify API credentials and permissions.
- Ensure date strings and other inputs conform to expected formats.
- Use the cursor property properly to paginate through large datasets.
Links and References
- NinjaOne API Documentation (general): https://api.ninjaone.com/docs
- NinjaOne Custom Fields API Reference (if available): [Not provided in source]
- n8n OAuth2 Credential Setup Guide: https://docs.n8n.io/credentials/oauth2/
Note: The exact API endpoint path for this operation is not explicitly shown in the bundled code snippet but is inferred from the operation name and typical REST conventions.