Actions159
- Related Items Actions
- Backup Actions
- Queries Actions
- Get Disk Drives
- Get Operating Systems
- Get RAID Controller Report
- Get Volumes
- Get Computer Systems
- Get Antivirus Status Report
- Get Device Health Report
- Get Custom Fields Report
- Get Installed Software Patches
- Get Custom Fields Detailed Report
- Get Installed OS Patches
- Get Pending Failed Rejected OS Patches
- Get RAID Drive Report
- Get Windows Services Report
- Get Antivirus Threats
- Get Device Usage
- Get Network Interfaces
- Get Processors
- Get Software
- Get Last Logged On Users Report
- Get Policy Overrides 1
- Get Scoped Custom Fields Report
- Get Pending Failed Rejected Software Patches
- Get Scoped Custom Fields Detailed Report
- System Actions
- Knowledge Base Articles Actions
- Get Knowledge Base Article Signed Urls
- Get Related Item Attachments Signed Urls
- Download Knowledge Base Article
- Get Knowledge Base Folder Path Content
- Upload Temp Attachments
- Get Knowledge Base Folder Content
- Get Client Knowledge Base Articles
- Upload Knowledge Base Articles
- Get Global Knowledge Base Articles
- Download Related Item Attachment
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Organization Checklists Actions
- Location Actions
- Management Actions
- Get Custom Fields Policy Condition
- Delete Policy Condition
- Reset Alert
- Update Device
- Request Scripting Options
- Submit OS Patch Scan
- Get Installer For Location
- Get Windows Event Policy Conditions
- Create Organization
- Cancel Device Maintenance
- Reboot Devices
- Set Windows Service Configuration
- Create Location For Organization
- Update Node Role Policy Assignment For Organization
- Create Windows Event Policy Condition
- Node Approval Operation
- Control Windows Service
- Remove Device Owner
- Submit OS Patch Apply
- Get Installer
- Create Policy
- Get Windows Event Policy Condition
- Update Device Maintenance
- Reset Policy Overrides
- Set Device Owner
- Submit Software Patch Scan
- Update Location
- Reset Alert Set Activity Data
- Get Device Link
- Run Script On Device
- Submit Software Patch Apply
- Update Organization
- Create Custom Fields Policy Condition
- Get Custom Fields Policy Conditions
- Custom Fields Actions
- Ticketing Actions
- Organization Actions
- Devices Actions
- Get Device Active Jobs
- Get Device Installed Software Patches
- Get Device Processors
- Update Node Attribute Values
- Get Device Disk Drives
- Get Device Pending Failed Rejected OS Patches
- Get Device Volumes
- Get Device Alerts
- Get Device Network Interfaces
- Get Device Software
- Get Device Activities
- Get Device Last Logged On User
- Get Device Services
- Get Policy Overrides
- Get Device
- Get Device Installed OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Node Custom Fields
- Groups Actions
- Webhooks Actions
Overview
This node interacts with the AvantGuard NinjaOne system API to retrieve device global custom fields. Specifically, the "Get Device Global Custom Fields" operation fetches custom fields that are globally defined for devices within the system. This is useful when you want to programmatically access metadata or additional attributes assigned to devices, which can be used for reporting, filtering, or automation purposes.
Practical examples include:
- Pulling all custom fields to display in a dashboard.
- Using custom field data to trigger workflows based on device attributes.
- Synchronizing device metadata with other systems.
Properties
| Name | Meaning |
|---|---|
| Additional Query Parameters | Optional parameters to customize the query. Currently supports: |
| - Scopes: Comma-separated list of scopes to filter the custom fields. Default is "all,node,location,organization". |
Output
The node outputs JSON data containing the device global custom fields retrieved from the NinjaOne API. The structure typically includes details about each custom field such as its name, type, scope, and possibly values or options associated with it.
If the node supports binary data output (not indicated here), it would represent any file or media content returned by the API, but this operation primarily deals with JSON metadata.
Dependencies
- Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
- Needs the base URL of the NinjaOne API configured in the credentials.
- Depends on the
@avantguardllc/n8n-openapi-nodepackage for OpenAPI integration. - Uses the OpenAPI specification defined in the bundled
openapi.jsonfile.
Troubleshooting
Common issues:
- Authentication failures due to invalid or missing API keys.
- Incorrect base URL configuration leading to connection errors.
- Invalid scope values causing empty or error responses.
Error messages:
- 401 Unauthorized: Check that the API key credential is correctly set and has necessary permissions.
- 404 Not Found: Verify the endpoint URL and resource names.
- 400 Bad Request: Ensure that query parameters like scopes are valid and properly formatted.
Links and References
- AvantGuard NinjaOne API Documentation (general reference for API endpoints and authentication)
- n8n Documentation for guidance on using credentials and configuring nodes with API integrations