NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Queries → Get Antivirus Threats

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve antivirus threat data based on specified query parameters. It is designed to fetch detailed information about detected antivirus threats filtered by device, timestamp, pagination cursor, and page size.

Common scenarios where this node is beneficial include:

  • Monitoring antivirus threats across devices in an IT environment.
  • Integrating threat data into security dashboards or incident response workflows.
  • Automating periodic retrieval of antivirus threat logs for compliance or auditing purposes.

For example, a user can configure the node to get all antivirus threats detected on a specific device since a certain timestamp, limiting results per page to manage large datasets efficiently.

Properties

Name Meaning
Df Device filter: Specify a device identifier to filter antivirus threats related to that device.
Ts Monitoring timestamp filter: Filter threats based on a specific monitoring timestamp.
Cursor Cursor name: Used for pagination to continue fetching results from a specific point.
Page Size Limit number of records per page: Controls how many threat records are returned per request.

Output

The node outputs JSON data containing the antivirus threat information retrieved from the NinjaOne API. The structure corresponds directly to the API's response format for antivirus threats, typically including details such as threat identifiers, affected devices, timestamps, threat types, and statuses.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the NinjaOne API using OAuth2 authentication.
  • The node depends on proper configuration of the NinjaOne API credentials within n8n.
  • Network access to the NinjaOne API endpoint is necessary.

Troubleshooting

  • Empty or incomplete results: Ensure that the device filter (Df) and timestamp (Ts) parameters are correctly set and correspond to existing data in NinjaOne.
  • Authentication errors: Verify that the OAuth2 credentials are valid and have not expired.
  • Pagination issues: If using the Cursor parameter, ensure it is correctly obtained from previous responses to paginate through results.
  • Missing binary data error: Not applicable here since this operation does not handle binary data.
  • API rate limits: Be aware of NinjaOne API rate limits which may cause request failures; implement retry logic or reduce request frequency if needed.

Links and References

Discussion