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 RAID Drive Report
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve a RAID Drive Report based on specified query parameters. It is useful for IT administrators or system monitoring workflows that need to fetch detailed RAID drive status and performance data from NinjaOne's monitoring system. For example, you can filter reports by device, timestamp, or paginate through large datasets.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: specify a device identifier or name to filter the RAID drive report data. |
| Ts | Monitoring timestamp filter: filter the report by a specific monitoring timestamp. |
| Cursor | Cursor name: used for pagination to continue fetching subsequent pages of results. |
| Page Size | Limit number of records per page: controls how many records are returned in one response. |
Output
The node outputs JSON data containing the RAID drive report retrieved from the NinjaOne API. The structure corresponds directly to the API response, typically including details about RAID drives such as status, health, performance metrics, and related metadata.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n.
- Depends on network connectivity to the NinjaOne API endpoint.
- Uses the NinjaOne API version 2 endpoints internally.
Troubleshooting
Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Incorrect filter values (e.g., invalid device ID or timestamp format) may result in empty responses or errors.
- Pagination parameters like cursor and page size must be used correctly to avoid missing data or infinite loops.
Error messages:
- Authentication errors: Ensure the NinjaOne API OAuth2 credential is valid and has not expired.
- Request errors: Check that all required query parameters are correctly formatted.
- Binary data errors do not apply here since this operation does not handle binary inputs.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n OAuth2 Credential Setup (for configuring NinjaOne API credentials)