Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
Queries → Get Device Usage
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve device usage data. Specifically, the "Get Device Usage" operation under the "Queries" resource fetches information about device usage statistics, which can be useful for IT administrators or support teams monitoring device activity within an organization.
Common scenarios include:
- Monitoring how devices are being used across a network.
- Generating reports on device activity for auditing or compliance.
- Integrating device usage data into dashboards or other workflow automations.
For example, an IT admin could use this node to paginate through device usage records, optionally including deleted devices, to analyze trends or identify inactive devices.
Properties
| Name | Meaning |
|---|---|
| Cursor | A cursor string used for pagination to specify the starting point of the next page. |
| Page Size | The maximum number of device usage records to return per page. |
| Include Deleted Devices | Boolean flag indicating whether to include devices that have been deleted in the results. |
Output
The node outputs JSON data containing the device usage information retrieved from the NinjaOne API. The structure typically includes device usage records and pagination metadata (such as cursors) to allow fetching subsequent pages.
If binary data were involved, it would be summarized here, but this operation deals only with JSON data.
Dependencies
- Requires an API authentication token credential configured in n8n to authenticate requests against the NinjaOne API.
- The node uses the NinjaOne OAuth2 API credential for authorization.
- No additional external dependencies beyond the NinjaOne API and n8n's HTTP request capabilities.
Troubleshooting
- Empty or missing data: Ensure that the cursor and page size parameters are set correctly. An incorrect cursor may result in no data returned.
- Authentication errors: Verify that the API key or OAuth2 credentials are valid and have sufficient permissions.
- API rate limits: If many requests are made rapidly, the NinjaOne API might throttle requests; implement delays or error handling accordingly.
- Missing binary data error: Although not applicable for this operation, if you switch to operations requiring binary input, ensure the binary property name matches the input data.
Links and References
- NinjaOne API Documentation (general reference for endpoints and parameters)
- n8n Documentation - Creating Custom Nodes