AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node interacts with the AvantGuard NinjaOne API to retrieve device health reports. Specifically, the "Get Device Health Report" operation under the "Queries" resource allows users to fetch detailed health status information about devices managed within the NinjaOne platform. This is useful for IT administrators or support teams who want to monitor device conditions, filter devices by health status, and paginate through large sets of device data.

Practical examples include:

  • Fetching all devices currently marked as unhealthy to prioritize troubleshooting.
  • Filtering devices by specific criteria such as device type or health status.
  • Paginating through device health records when dealing with a large number of devices.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination controls for the query:
- Df Device filter (string) to narrow down which devices to include in the report.
- Health Health status filter (string) to select devices based on their health condition.
- Cursor Cursor name (string) used for pagination to continue fetching results from a specific point.
- Page Size Number (integer) limiting how many records are returned per page.

Output

The node outputs JSON data containing the device health report retrieved from the NinjaOne API. The structure typically includes an array of device health records, each detailing device identifiers, health status, and possibly other metadata depending on the API response.

If the API supports pagination, the output may also include cursor or paging tokens to facilitate fetching subsequent pages.

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

Troubleshooting

  • Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
  • Invalid query parameters: Verify that filters like "Df" and "Health" use valid values recognized by the NinjaOne API.
  • Pagination issues: When using the "Cursor" parameter, ensure it matches a valid cursor token from a previous response.
  • Empty responses: Could indicate no devices match the given filters; try broadening or removing filters.
  • Network or API errors: Check connectivity and NinjaOne service status.

Links and References

Discussion