Actions32
- Device Actions
- Control Windows Service
- Get
- Get Activities
- Get Alerts
- Get Custom Fields
- Get Dashboard URL
- Get Disks
- Get Jobs
- Get Last Logged On User
- Get Many
- Get Network Interfaces
- Get OS Patch Installs
- Get OS Patches
- Get Policy Overrides
- Get Processors
- Get Software
- Get Software Patch Installs
- Get Software Patches
- Get Volumes
- Get Windows Services
- Reboot Device
- Run Script
- Update Custom Fields
- Ticket Actions
- Organization Actions
Device → Get Custom Fields
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve custom fields associated with a specific device. It is useful in scenarios where you need to fetch detailed, customized metadata or attributes that have been defined for devices within the NinjaOne platform. For example, it can be used to pull custom configuration details or tags assigned to a device for reporting or automation purposes.
Use Case Examples
- Fetch custom fields for a device to display in a dashboard.
- Retrieve device-specific custom attributes to use in an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Device ID | The unique identifier of the device for which custom fields are to be retrieved. |
| Request Options | Additional request settings such as batching, SSL certificate validation, proxy configuration, and timeout settings. |
Output
JSON
customFields- The custom fields data retrieved for the specified device.
Dependencies
- NinjaOne API with OAuth2 authentication
Troubleshooting
- Ensure the Device ID is correct and exists in the NinjaOne system to avoid 'not found' errors.
- Check network connectivity and proxy settings if requests time out or fail.
- If SSL certificate errors occur, consider enabling the option to ignore SSL issues, but be aware of security implications.
- Verify that the OAuth2 credentials are valid and have the necessary permissions to access device custom fields.
Links
- NinjaOne API Documentation - Official API documentation for NinjaOne, useful for understanding available endpoints and data structures.