Actions120
- Alert Actions
- Backup Actions
- Custom Field Actions
- Device Actions
- Document Template Actions
- Group Actions
- Knowledge Base Article Actions
- Location Actions
- Organization Actions
- Organization Document Actions
- Query Actions
- Alerts
- Antivirus Status
- Antivirus Threats
- Backup Usage
- Computer Systems
- Custom Fields
- Custom Fields (Detailed)
- Device Health
- Disks
- Logged-On Users
- Network Interfaces
- Operating Systems
- OS Patch Installs
- OS Patches
- Policy Overrides
- Processors
- RAID Controllers
- RAID Drives
- Scoped Custom Fields
- Scoped Custom Fields (Detailed)
- Software
- Software Patch Installs
- Software Patches
- Volumes
- Windows Services
- Related Item Actions
- Software License Actions
- System Actions
- Get Activities
- Get Contacts
- Get Device Custom Fields
- Get Device Roles
- Get Devices (Detailed)
- Get End Users
- Get Jobs
- Get Locations
- Get Notification Channels
- Get Notification Channels (Enabled)
- Get Organizations (Detailed)
- Get Policies
- Get Scheduled Tasks
- Get Scripting Languages
- Get Scripts
- Get Software Products
- Get Technicians
- Get User Roles
- Ticketing Actions
- User Actions
- Webhook Actions
Query → Antivirus Threats
AI-generatedSummary
Queries NinjaOne for antivirus threat records. Use the filters to narrow results by pagination, monitoring timestamp, or device attributes.
Inputs
- Authentication (required) — Choose OAuth2 (Authorization Code, default) or Client Credentials and configure the matching NinjaOne credentials.
- Filters — Optional query parameters: Cursor for pagination, Page Size (default 200), and Timestamp for monitoring data. Device filters can restrict by approval status, device class, comma-separated device IDs, location IDs, organization IDs, role IDs, or online status. Device filters are combined into NinjaOne's device filter expression.
Output shape
A list of items, with each returned threat record as an item’s JSON data.
The node makes one GET request to NinjaOne’s antivirus-threats query endpoint and passes the configured filters as query parameters. It does not automatically fetch subsequent pages; use the cursor to paginate. If the API returns a non-array response, it is emitted as one item.