NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Devices → Get Node Custom Fields

AI-generated

Overview

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

Discussion