AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve information about processors via the "Get Processors" operation under the "Queries" resource. It is useful for scenarios where you need to monitor or analyze hardware details of devices managed by NinjaOne, such as gathering processor data for inventory management, performance monitoring, or reporting.

For example, an IT administrator could use this node to fetch processor details filtered by device or timestamp to generate up-to-date hardware reports or to track changes in device configurations over time.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination controls that can be added to refine the query results. These include:
- Df: Device filter (string)
- Ts: Monitoring timestamp filter (string)
- Cursor: Cursor name for pagination (string)
- Page Size: Limit number of records per page (number)

Output

The node outputs JSON data containing the list of processors retrieved from the NinjaOne API according to the specified filters. The structure corresponds to the API response for processor queries, typically including processor attributes such as model, speed, cores, and related metadata.

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.
  • The node depends on the @avantguardllc/n8n-openapi-node package and the OpenAPI specification (openapi.json) bundled within the node implementation.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Invalid query parameters: Verify that optional filters like device filter (df) and timestamp (ts) are correctly formatted.
  • Pagination issues: When using cursor and page size, ensure values are valid to avoid empty or incomplete results.
  • Network or API errors: Check connectivity to the NinjaOne API endpoint and confirm the base URL is correct.

Links and References

Discussion