NinjaOne icon

NinjaOne

Consume NinjaOne API

Actions158

Queries → Get Volumes

AI-generated

Overview

This node interacts with the NinjaOne API to retrieve volume information based on specified query parameters. It is useful for IT administrators or system monitoring workflows that need to fetch detailed volume data from managed devices, such as disk usage, status, or encryption details.

Typical use cases include:

  • Monitoring disk volumes across multiple devices.
  • Filtering volumes by device name or timestamp.
  • Paginating through large sets of volume records.
  • Including additional metadata like BitLocker status in the results.

Properties

Name Meaning
Df Device filter: specify a device identifier or name to limit the query to that device.
Ts Monitoring timestamp filter: filter volumes 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 volume records are returned per call.
Include Additional information to include: e.g., "bl" to include BitLocker status in the response.

Output

The node outputs an array of JSON objects representing volume data retrieved from the NinjaOne API. Each object contains volume details according to the applied filters and includes any additional requested information (such as BitLocker status).

If binary data were involved, it would be summarized here, but this operation only returns JSON data.

Dependencies

  • Requires an active connection to the NinjaOne API using OAuth2 authentication.
  • The node depends on the NinjaOne API endpoint /v2/queries/volumes (implied by the resource and operation).
  • Properly configured credentials with necessary permissions to access volume data.
  • No additional environment variables are explicitly required beyond standard n8n credential setup.

Troubleshooting

  • Empty results: Check if the device filter (Df) or timestamp (Ts) values are correct and correspond to existing data.
  • Pagination issues: Ensure the Cursor and Page Size parameters are used correctly to navigate through paged results.
  • API errors: Authentication failures may occur if the OAuth2 token is expired or invalid; re-authenticate the credential.
  • Invalid include parameter: Using unsupported values in Include may result in incomplete or error responses; verify allowed options (e.g., "bl" for BitLocker).
  • Missing input data: If required parameters are not set or incorrectly typed, the API request may fail or return unexpected results.

Links and References

Discussion