AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve information about computer systems. Specifically, the "Get Computer Systems" operation under the "Queries" resource allows users to fetch details about managed devices or endpoints in their environment. This can be useful for IT administrators who want to monitor device status, inventory hardware, or gather system data for reporting and management purposes.

Practical examples include:

  • Fetching a list of all computer systems currently monitored.
  • Filtering devices based on specific criteria such as device type or monitoring timestamp.
  • Paginating through large sets of device records to process them incrementally.

Properties

Name Meaning
Additional Query Parameters Optional parameters 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 representing the retrieved computer systems. The structure typically includes an array of device objects with their respective properties as returned by the NinjaOne API. Each object may contain details such as device identifiers, status, timestamps, and other metadata relevant to the computer systems.

If the API supports binary data (e.g., file attachments or reports), the node would handle it accordingly, but based on the provided code and operation, the output is primarily JSON-formatted system data.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne service.
  • The base URL for the API must be configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for building request properties from the OpenAPI specification.

Troubleshooting

  • Authentication errors: Ensure that 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 formatted correctly according to the API documentation.
  • Pagination issues: When using cursor and page size parameters, ensure proper handling of cursors returned by previous requests to avoid missing or duplicating records.
  • Network or API downtime: Check network connectivity and the status of the NinjaOne API service if requests fail unexpectedly.

Links and References

Discussion