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
Location → Get Node Custom Fields 2
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve custom fields associated with a specific Location resource. The operation "Get Node Custom Fields 2" fetches custom field values for a given node ID and location ID, optionally including inherited values based on a definition scope hierarchy.
Typical use cases include:
- Retrieving detailed metadata or custom attributes assigned to a particular location within an IT management system.
- Automating workflows that depend on custom configuration or classification data stored in NinjaOne locations.
- Integrating location-specific custom field data into other systems or reports.
For example, you might use this node to get all custom fields for a location representing a physical office site, including inherited settings from parent definitions, to tailor asset management or compliance checks.
Properties
| Name | Meaning |
|---|---|
| Id | Numeric identifier of the node whose custom fields are being retrieved. |
| Location Id | Numeric identifier of the location for which custom fields are requested. |
| With Inheritance | Boolean flag indicating whether to retrieve custom field values using definition scope hierarchy (i.e., include inherited values). Defaults to true. |
Output
The node outputs an array of JSON objects, each containing the response from the NinjaOne API call for the requested custom fields. The structure corresponds directly to the API's returned data for custom fields on the specified node and location.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n for authentication.
- Depends on the NinjaOne API endpoint
/v2/locations/{locationId}/nodes/{id}/custom-fields(implied by the operation name and parameters). - Network connectivity to the NinjaOne API service.
Troubleshooting
- Missing or invalid credentials: Ensure the NinjaOne API OAuth2 credential is correctly set up and authorized.
- Invalid IDs: Providing non-existent or incorrect
IdorLocation Idvalues will result in API errors or empty responses. - Binary data errors: Not applicable here since this operation does not handle binary data.
- API rate limits or downtime: Temporary failures may occur if the NinjaOne API enforces rate limits or experiences outages; retry logic or error handling should be considered.
- Error messages: If the node throws errors related to request failures, verify network access and credential validity.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes
- OAuth2 Authentication in n8n