NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Queries → Get Policy Overrides 1

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve policy override data based on specified query parameters. It is designed to fetch paginated lists of policy overrides, optionally filtered by device and controlled via cursor-based pagination.

Common scenarios include:

  • Retrieving a list of policy overrides for auditing or reporting.
  • Fetching subsets of policy overrides incrementally using cursors.
  • Filtering policy overrides by specific devices.

Practical example: A user wants to get all policy overrides related to a particular device, limiting results to 1000 per page, and using a cursor to paginate through large result sets.

Properties

Name Meaning
Df Device filter - a string used to filter policy overrides by device identifier or name.
Cursor Cursor name - a string used for cursor-based pagination to fetch subsequent pages.
Page Size Limit number of records per page - a number specifying how many records to return per request (default 1000).

Output

The node outputs an array of JSON objects representing the retrieved policy overrides from the NinjaOne API. Each item in the output corresponds to one response from the API call containing policy override data.

The json field contains the full API response parsed as JSON. There is no binary data output for this operation.

Dependencies

  • Requires an active connection to the NinjaOne API authenticated via OAuth2 credentials.
  • The node uses the NinjaOne API endpoint /v2/policies/overrides (implied by the operation context) with query parameters for filtering and pagination.
  • Proper configuration of the OAuth2 credential within n8n is necessary for authentication.

Troubleshooting

  • No data returned: Check that the device filter (Df) is correct and matches existing devices. Also verify that the cursor is valid if used.
  • Authentication errors: Ensure the OAuth2 credentials are correctly set up and have not expired.
  • API rate limits: If many requests are made quickly, the NinjaOne API may throttle requests; implement delays or handle retries accordingly.
  • Invalid parameter values: Passing invalid types or empty strings where not allowed may cause API errors.

Common error messages:

  • "No binary data exists on item!" or "No binary data property ... does not exist" — Not applicable here since this operation does not use binary data.
  • API error messages will be returned in the json.error field if continueOnFail is enabled.

Links and References

Discussion