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 Disk Drives
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve information about disk drives using the "Get Disk Drives" operation under the "Queries" resource. It allows users to query disk drive data filtered by device, timestamp, cursor for pagination, and page size limits. This is useful in IT management scenarios where monitoring and reporting on disk usage or status across multiple devices is required.
Practical examples include:
- Fetching disk drive details for a specific device to monitor storage health.
- Retrieving disk drive data at a particular monitoring timestamp to analyze historical states.
- Paginating through large sets of disk drive records for comprehensive asset management.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: Specify a device identifier to filter disk drives related to that device. |
| Ts | Monitoring timestamp filter: Filter results 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 disk drive records are returned per request. |
Output
The node outputs an array of JSON objects representing the disk drive data retrieved from the NinjaOne API. Each item in the output corresponds to a disk drive record matching the specified filters and pagination parameters.
The json field contains the raw response data from the API call, which typically includes details such as device identifiers, disk drive attributes, usage statistics, and timestamps.
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the NinjaOne API via an OAuth2 API credential configured in n8n.
- The node uses the NinjaOne API endpoints to fetch disk drive data.
- Proper API authentication credentials must be set up in n8n before using this node.
Troubleshooting
- Empty or missing results: Ensure that the filter parameters (device, timestamp) are correctly specified and that the NinjaOne account has relevant data.
- Authentication errors: Verify that the OAuth2 API credential is valid and has not expired.
- Pagination issues: If using the cursor property, ensure it is correctly obtained from previous responses; otherwise, no further pages will be fetched.
- Invalid parameter values: Check that numeric values like page size are positive integers and strings like device filters match expected formats.
Common error messages may include:
- Authentication failures due to invalid or missing tokens.
- API rate limiting or quota exceeded errors.
- Invalid parameter errors if unsupported values are provided.
Resolving these usually involves checking credentials, adjusting input parameters, or consulting NinjaOne API documentation for limits.
Links and References
- NinjaOne API Documentation
- n8n OAuth2 Credential Setup
- NinjaOne Disk Drive Monitoring Concepts (hypothetical link for context)