AvantGuard - NinjaOne icon

AvantGuard - NinjaOne

AvantGuard - NinjaOne

Actions159

Overview

This node interacts with the "Devices" resource of the AvantGuard NinjaOne API to retrieve volume information for a specific device. It is useful in scenarios where you need detailed storage or volume data about managed devices, such as monitoring disk usage, checking BitLocker status, or auditing device storage configurations.

For example, an IT administrator could use this node to fetch all volumes on a particular device to verify encryption status or available space before deploying software updates.

Properties

Name Meaning
Id The unique identifier of the device for which to retrieve volume information.
Additional Query Parameters Optional parameters to customize the query. Currently supports: include - additional information to include, e.g., "bl" for BitLocker status.

Output

The node outputs JSON data representing the volumes associated with the specified device. This typically includes details such as volume names, sizes, free space, and optionally extended information like BitLocker encryption status if requested via the include parameter.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the AvantGuard NinjaOne API.
  • The base URL for the API must be configured in the node credentials.
  • Depends on the @avantguardllc/n8n-openapi-node package and the corresponding OpenAPI specification bundled within the node.

Troubleshooting

  • Invalid Device Id: If the provided device ID does not exist or is incorrect, the API will likely return an error or empty result. Verify the device ID before running the node.
  • Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions to access device volume data.
  • Incorrect include Parameter: Passing unsupported values in the include field may cause the API to ignore the parameter or return errors. Use documented options like "bl" for BitLocker status.
  • Network Issues: Connectivity problems to the API endpoint can cause timeouts or failures. Check network settings and API availability.

Links and References

Discussion