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
Devices → Get Node Custom Fields
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve custom fields defined on a specific device node. It is useful when you want to programmatically access additional metadata or custom attributes associated with devices managed in NinjaOne. For example, you might use this node to fetch custom configuration details or tags assigned to a device for reporting or automation workflows.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the device for which to retrieve custom fields (a number). |
| With Inheritance | Boolean flag indicating whether to retrieve custom field values using the definition scope hierarchy (true/false). |
Output
The node outputs an array of JSON objects, each representing the response from the NinjaOne API call that fetches the custom fields for the specified device. The structure corresponds directly to the API's returned data for device custom fields, typically including field names, values, and possibly metadata about inheritance if requested.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API via an OAuth2 authentication credential.
- The node uses the NinjaOne API endpoint
/v2/devices/{id}/custom-fields(inferred from the operation context) to fetch data. - Proper API permissions are necessary to read device custom fields.
- No additional environment variables are explicitly required beyond the configured API credentials.
Troubleshooting
- Missing or invalid device Id: Ensure the "Id" property is set correctly as a number corresponding to an existing device in NinjaOne.
- Authentication errors: Verify that the OAuth2 credential is valid and has not expired.
- API permission issues: Confirm that the connected API user has rights to read device custom fields.
- Empty or unexpected responses: Check if the device actually has custom fields defined; also verify the "With Inheritance" flag usage as it may affect returned data.
- Binary data errors: Not applicable here since this operation does not handle binary data.
Common error messages will relate to HTTP request failures, such as 401 Unauthorized (authentication), 404 Not Found (invalid device id), or 403 Forbidden (insufficient permissions).
Links and References
- NinjaOne API Documentation (general reference for endpoints and authentication)
- n8n Documentation - Creating Custom Nodes