AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node integrates with the AvantGuard NinjaOne API to retrieve antivirus threat data. Specifically, the "Get Antivirus Threats" operation under the "Queries" resource allows users to fetch detailed information about detected antivirus threats within their monitored environment.

Common scenarios for this node include:

  • Security monitoring workflows where you want to automatically gather and analyze antivirus threat data.
  • Incident response automation that triggers alerts or remediation steps based on recent threats.
  • Reporting and auditing tasks that require up-to-date threat intelligence from endpoint devices.

For example, a user could configure this node to periodically pull the latest antivirus threats filtered by device or timestamp, then use the data to update dashboards or trigger notifications.

Properties

Name Meaning
Additional Query Parameters Optional filters and pagination controls for the query. Includes:
Df: Device filter (string)
Ts: Monitoring timestamp filter (string)
Cursor: Cursor name for pagination (string)
Page Size: Limit number of records per page (number)

These parameters allow fine-tuning of the request to retrieve specific subsets of antivirus threat data or control the volume of results returned.

Output

The node outputs JSON data representing antivirus threat records retrieved from the API. Each item in the output corresponds to an individual threat entry containing details such as affected device, threat type, detection time, and other relevant metadata.

No binary data output is indicated for this operation.

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 and handling API communication.

Troubleshooting

  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Empty or incomplete data: Verify that optional query parameters like device filter or timestamp are correctly specified; incorrect filters may result in no matching records.
  • Pagination issues: When retrieving large datasets, use the cursor and page size parameters properly to paginate through results.
  • Network or API errors: Check network connectivity and confirm the base URL is correct and accessible.

Links and References

Discussion