AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne platform to retrieve alerts related to a specific device. It is useful for IT administrators or support teams who want to monitor device health, security events, or other alert conditions programmatically within an automation workflow. For example, you can use this node to fetch recent alerts for a workstation or server to trigger notifications or further automated remediation steps.

Properties

Name Meaning
Id The unique identifier of the device for which to retrieve alerts (required).
Additional Query Parameters Optional parameters to customize the query:
- Lang Language tag to specify the language of the response.
- Tz Time zone to adjust timestamps in the response.

Output

The node outputs JSON data containing the alerts associated with the specified device. Each alert typically includes details such as alert type, severity, timestamp, and description. This structured output allows downstream nodes to process or filter alerts as needed.

If the API supports binary data (e.g., attachments related to alerts), it would be included in the binary output field, but based on the provided code and properties, the primary output is JSON-formatted alert information.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne platform.
  • Needs the base URL of the NinjaOne API configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the OpenAPI specification (openapi.json) bundled with the node for request building.

Troubleshooting

  • Missing or invalid device ID: Ensure the "Id" property is set correctly to a valid device identifier; otherwise, the API call will fail.
  • Authentication errors: Verify that the API key credential is properly configured and has sufficient permissions.
  • Incorrect additional query parameters: If using "Lang" or "Tz", ensure values conform to expected formats (e.g., valid language tags or time zone identifiers).
  • Network or API endpoint issues: Confirm the base URL is correct and the NinjaOne service is reachable.

Common error messages may include authentication failures, resource not found (invalid device ID), or bad request due to malformed query parameters.

Links and References

Discussion