Actions30
- Device Actions
- Ticket Actions
- Organization Actions
- Document Actions
Overview
The node integrates with the NinjaOne API to retrieve information about disks associated with a specific device. This operation is useful in IT management and monitoring scenarios where you need to gather detailed hardware information from managed devices, such as checking disk health, capacity, or configuration.
Practical examples include:
- Automatically fetching disk details for inventory management.
- Monitoring disk usage or status as part of an automated alerting workflow.
- Integrating disk data into asset management or reporting systems.
Properties
| Name | Meaning |
|---|---|
| Device ID | The unique identifier of the device whose disks you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing details about the disks of the specified device. The exact structure depends on the NinjaOne API response but typically includes disk attributes such as disk name, size, type, status, and other relevant metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the NinjaOne API.
- Requires an API authentication token configured in n8n credentials (an OAuth2 API key credential).
- The base URL for the API can be customized via credentials; otherwise, it defaults to
https://api.ninjaone.com.
Troubleshooting
Common issues:
- Invalid or missing Device ID will cause the request to fail.
- Authentication errors if the API token is invalid or expired.
- Network connectivity issues preventing access to the NinjaOne API.
Error messages:
- Unauthorized or 401 errors indicate problems with API credentials; verify and refresh the API key.
- 404 Not Found may indicate the device ID does not exist or is incorrect.
- Rate limiting or 429 errors require waiting or adjusting request frequency.
Links and References
- NinjaOne API Documentation (for detailed API endpoints and data structures)
- n8n documentation on creating custom nodes