AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

The node integrates with the AvantGuard NinjaOne API to retrieve a scoped custom fields report. Specifically, the "Get Scoped Custom Fields Report" operation under the "Queries" resource fetches detailed information about custom fields filtered by various criteria such as scope, update time, and pagination.

This node is useful in scenarios where users need to programmatically access metadata about custom fields configured in NinjaOne, for example:

  • Synchronizing custom field definitions with another system.
  • Auditing or reporting on custom fields usage and configuration.
  • Extracting secure or non-secure custom field values for analysis.

Properties

Name Meaning
Additional Query Parameters Optional parameters to refine the query results:
- Cursor Cursor name for pagination control.
- Page Size Limit number of records per page (default 1000).
- Updated After Filter to include only custom fields updated after this date (ISO string).
- Fields Comma-separated list of specific fields to return in the response.
- Scopes Comma-separated list of scopes to filter by (default is "all").
- Show Secure Values Boolean flag indicating if secure values should be returned as plain text without encryption (default true).

Output

The node outputs JSON data representing the scoped custom fields report retrieved from the NinjaOne API. The structure includes details about each custom field according to the requested filters and fields.

If secure values are included (when Show Secure Values is true), these will be presented as plain text rather than encrypted or masked.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
  • The base URL for the API must be configured in the node credentials.
  • The node depends on the @avantguardllc/n8n-openapi-node package and the bundled OpenAPI specification (openapi.json) for request construction.

Troubleshooting

  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • Invalid query parameters: Check that date strings are correctly formatted (ISO 8601) and that numeric values like Page Size are within allowed ranges.
  • Empty responses: May occur if filters exclude all data; verify the correctness of Scopes, Updated After, and other parameters.
  • Pagination issues: Use the Cursor parameter properly to navigate through paged results.

Links and References

Discussion