AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve detailed reports on custom fields related to queries. Specifically, the "Get Custom Fields Detailed Report" operation fetches comprehensive information about custom fields, which can be filtered and paginated using various query parameters.

This node is useful in scenarios where users need to analyze or export metadata about custom fields for devices or other entities managed within NinjaOne. For example, IT administrators might use it to audit custom field configurations, track changes over time, or integrate this data into reporting dashboards.

Properties

Name Meaning
Additional Query Parameters Optional parameters to refine the report:
- Df: Device filter (string)
- Cursor: Cursor name for pagination (string)
- Page Size: Limit number of records per page (number, default 1000)
- Updated After: Filter for custom fields updated after a specific date (string)
- Fields: Comma-separated list of fields to include (string)
- Show Secure Values: Whether to return secure values as plain text without encryption (boolean, default true)

Output

The node outputs JSON data containing the detailed report of custom fields according to the specified query parameters. The structure typically includes an array of custom field objects with their properties and values as returned by the NinjaOne API.

If secure values are included (depending on the Show Secure Values flag), these will be presented in plain text rather than encrypted form.

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 corresponding OpenAPI specification (openapi.json) bundled internally.

Troubleshooting

  • Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions to access custom field reports.
  • Invalid query parameters: Passing unsupported or incorrectly formatted parameters (e.g., invalid date format for Updated After) may cause API errors. Validate inputs before execution.
  • Pagination issues: If the result set is large, use the Cursor and Page Size parameters properly to paginate through results.
  • Empty results: If no data is returned, verify filters such as device filter (Df) or date filters to ensure they match existing data.

Links and References

Discussion