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
System → Get Device Global Custom Fields
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve device global custom fields filtered by specified scopes. It is useful when you want to fetch metadata or custom attributes associated with devices across different organizational levels such as nodes, locations, or organizations.
A practical example would be automating asset management workflows where you need to pull custom field data for devices to enrich reports or trigger further automation based on those fields.
Properties
| Name | Meaning |
|---|---|
| Scopes | Comma-separated list of scopes to filter the custom fields. The only available option is: "All Node Location Organization" (value: all,node,location,organization). |
Output
The node outputs JSON data containing the device global custom fields retrieved from the NinjaOne API. The structure corresponds to the API response and includes details about each custom field within the specified scopes.
No binary data output is produced by this operation.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests against the NinjaOne API.
- The node uses the NinjaOne OAuth2 API credential for authorization.
- Network access to the NinjaOne API endpoint is necessary.
Troubleshooting
Common issues:
- Missing or invalid API credentials will cause authentication failures.
- Providing unsupported scope values may result in empty or error responses.
- Lack of network connectivity to the NinjaOne API will cause request failures.
Error messages:
- Errors returned from the NinjaOne API are passed through; typical errors include unauthorized access or invalid parameters.
- If no binary data is found when expected (not applicable here), a specific error is thrown, but this operation does not handle binary data.
To resolve errors:
- Verify that the API key or OAuth2 credentials are correctly set up.
- Ensure the scopes parameter is correctly formatted and valid.
- Check network connectivity and NinjaOne service status.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and data structures)
- n8n Documentation (for general usage of custom nodes and credentials)