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 → Backup Usage
AI-generatedSummary
Query NinjaOne backup usage records with optional pagination and device filters. The operation sends a GET request to /api/v2/queries/backup/usage and returns the API response as n8n items.
Inputs
- authentication (required) — Choose OAuth2 (Authorization Code) or Client Credentials authentication.
- filters — Optional query parameters: cursor for pagination, pageSize (default 200), and ts for a monitoring timestamp. You can also filter devices by approval status, device classes, comma-separated device IDs, location IDs, organization IDs, or role IDs, and by online status. Device filters are combined into a NinjaOne
dfexpression.
Output shape
A list of n8n items, with each returned record in an item's json field.
The request is made once; this operation does not automatically fetch subsequent cursor pages. A non-array API response is returned as one item. If the API response is empty or undefined, the node emits `{ "success": true }.