Actions32
- Device Actions
- Control Windows Service
- Get
- Get Activities
- Get Alerts
- Get Custom Fields
- Get Dashboard URL
- Get Disks
- Get Jobs
- Get Last Logged On User
- Get Many
- Get Network Interfaces
- Get OS Patch Installs
- Get OS Patches
- Get Policy Overrides
- Get Processors
- Get Software
- Get Software Patch Installs
- Get Software Patches
- Get Volumes
- Get Windows Services
- Reboot Device
- Run Script
- Update Custom Fields
- Ticket Actions
- Organization Actions
Device → Get Volumes
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve volume information for a specified device. It is useful in IT management scenarios where administrators need to monitor or manage storage volumes on devices remotely. For example, it can be used to fetch details about disk volumes on a device to check available space or volume health.
Use Case Examples
- Retrieve all volumes for a device by providing the device ID to monitor storage usage.
- Use the node to automate inventory management by collecting volume data across multiple devices.
Properties
| Name | Meaning |
|---|---|
| Device ID | The unique identifier of the device for which volume information is requested. |
| Request Options | Additional settings to control the request behavior, such as batching, SSL certificate validation, proxy settings, and timeout duration. |
Output
JSON
volumes- Array of volume objects retrieved from the specified device, containing details about each volume.
Dependencies
- NinjaOne API with OAuth2 authentication
Troubleshooting
- Ensure the provided Device ID is correct and the device is accessible via the NinjaOne API.
- Check network connectivity and proxy settings if requests fail or time out.
- If SSL certificate errors occur, consider enabling the option to ignore SSL issues, but be aware of security risks.
- Verify that the OAuth2 credentials are valid and have the necessary permissions to access device volume data.
Links
- NinjaOne API Documentation - Official API documentation for NinjaOne, useful for understanding available endpoints and data structures.