AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve policy override information related to queries. Specifically, the "Get Policy Overrides 1" operation under the "Queries" resource fetches policy override data, which can be useful for IT administrators or security teams who want to audit or review exceptions made to standard policies on devices managed by NinjaOne.

Common scenarios include:

  • Auditing device compliance by retrieving all policy overrides.
  • Filtering overrides by device or paginating through large sets of overrides.
  • Integrating policy override data into broader IT asset management or security workflows.

Example use case: An IT admin wants to generate a report of all policy overrides applied in the last month, filtered by specific devices, and then trigger alerts if any critical policies were overridden.

Properties

Name Meaning
Additional Query Parameters Optional parameters to refine the query results. Includes:
- Df: Device filter (string) to limit results to a specific device.
- Cursor: Cursor name (string) for pagination.
- Page Size: Number (default 1000) to limit the number of records returned per page.

Output

The node outputs JSON data representing the retrieved policy overrides. The structure corresponds to the API response from NinjaOne's "Get Policy Overrides" endpoint, typically including details such as override IDs, associated devices, policies overridden, timestamps, and possibly user information who applied the override.

No binary data output is indicated.

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.
  • Relies on the @avantguardllc/n8n-openapi-node package and the provided OpenAPI specification (openapi.json) for request building.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Empty or incomplete results: Verify that query parameters like device filter or cursor are correctly specified; incorrect values may yield no data.
  • Pagination issues: If many records exist, use the cursor and page size parameters properly to paginate through results.
  • API rate limits: Excessive requests might be throttled; implement retry logic or reduce request frequency.
  • Network errors: Check connectivity to the NinjaOne API endpoint and ensure the base URL is correct.

Links and References

Discussion