AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node operation "Get Node Custom Fields 2" under the "Location" resource is designed to retrieve custom field data associated with a specific location node. It allows users to fetch detailed metadata or custom attributes defined for a particular location entity within an external system.

Common scenarios where this node would be beneficial include:

  • Integrating location-specific custom data into workflows, such as pulling additional configuration or descriptive fields.
  • Automating reporting or synchronization tasks that require enriched location information.
  • Dynamically accessing extended properties of locations without hardcoding them in the workflow.

For example, a user might use this node to get custom tags or settings applied to a location before performing conditional logic or updating other systems accordingly.

Properties

Name Meaning
Id Numeric identifier of the node whose custom fields are to be retrieved.
Location Id Numeric identifier of the location associated with the node.
Additional Query Parameters Optional parameters to customize the query. Currently supports:
- With Inheritance: Boolean flag to indicate whether to retrieve values using definition scope hierarchy (true/false).

Output

The output of this node will be JSON data containing the custom fields associated with the specified location node. The structure typically includes key-value pairs representing each custom field and its value.

If the node supports binary data output, it would represent any attached files or media related to the custom fields, but based on the provided code and properties, the primary output is structured JSON data.

Dependencies

  • Requires an API key credential for authentication to the external AvantGuard NinjaOne service.
  • Depends on the base URL and headers configured in the node credentials.
  • Uses the @avantguardllc/n8n-openapi-node package and an OpenAPI specification (openapi.json) bundled with the node for request building and execution.

Troubleshooting

  • Missing or invalid IDs: Ensure that both the "Id" and "Location Id" properties are correctly set and correspond to existing entities in the external system.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions to access location custom fields.
  • Network or API errors: Check connectivity to the configured base URL and confirm the external service is operational.
  • Incorrect query parameters: If using "With Inheritance," ensure the boolean value is correctly set; otherwise, the returned data may not include inherited custom fields.

Links and References

Discussion