AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

The node integrates with the AvantGuard NinjaOne system API to retrieve device information. Specifically, the "Get Devices" operation fetches a list of devices managed by the system. This is useful for IT administrators or automation workflows that need to inventory devices, monitor their status, or trigger actions based on device data.

Practical examples include:

  • Automatically generating reports of all devices in an organization.
  • Filtering devices based on specific criteria (e.g., device type or ID) for targeted management.
  • Paginating through large device lists to process them in batches.

Properties

Name Meaning
Additional Query Parameters Optional parameters to refine the device query:
- Df: Device filter string.
- Page Size: Limit number of devices returned per request.
- After: Last Node ID from previous page for pagination.

Output

The node outputs JSON data representing the list of devices retrieved from the NinjaOne system. The structure typically includes device details such as IDs, names, and other metadata as provided by the API.

If the API supports binary data (not indicated here), it would be summarized accordingly, but this node primarily returns JSON device information.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
  • Needs the base URL of the NinjaOne API configured in credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package for OpenAPI integration.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect base URL configuration can lead to connection errors.
    • Using unsupported or malformed query parameters may result in API errors or empty responses.
    • Pagination parameters must be handled carefully to avoid missing or duplicating devices.
  • Error messages:

    • Authentication errors usually indicate invalid API keys; verify and update credentials.
    • HTTP 4xx or 5xx errors suggest issues with request parameters or server availability; check parameter correctness and API status.
    • Empty results might mean no devices match the filters; try broadening query parameters.

Links and References

Discussion