NinjaOneInstall

Overview

This node interacts with the NinjaOne API to retrieve information about device volumes. Specifically, the "Get Device Volumes" operation fetches volume details for a specified device by its identifier. This is useful in IT management scenarios where administrators need to monitor or audit storage volumes on managed devices, such as checking disk usage, volume labels, or encryption status.

Practical examples include:

• Retrieving all volumes on a workstation to verify available disk space.
• Checking BitLocker encryption status on device volumes for security compliance.
• Integrating volume data into asset management or reporting workflows.

Properties

Output

The node outputs an array of JSON objects, each representing the response from the NinjaOne API for the requested device volumes. The structure typically includes details about each volume on the device, such as volume name, size, free space, file system type, and optionally BitLocker encryption status if requested.

If binary data were involved (not in this operation), it would be indicated here, but this operation returns only JSON data.

Example output snippet (conceptual):

{
  "volumes": [
    {
      "name": "C:",
      "size": 500000000000,
      "freeSpace": 200000000000,
      "fileSystem": "NTFS",
      "bitLockerStatus": "Encrypted"
    },
    ...
  ]
}

Dependencies

• Requires an active NinjaOne API OAuth2 credential configured in n8n for authentication.
• Depends on network connectivity to the NinjaOne API endpoint.
• Uses the NinjaOne API version 2 endpoints under /v2/devices/{id}/volumes (implied from code pattern).

Troubleshooting

• Common issues:

  • Invalid or missing device Id will cause the API call to fail.
  • Lack of proper API credentials or expired tokens will result in authentication errors.
  • Requesting unsupported values in the "Include" property may lead to unexpected results or ignored parameters.

• Error messages:

  • "No binary data exists on item!" or similar will not occur here since this operation does not handle binary data.
  • API errors returned from NinjaOne will be passed through; ensure the device Id is correct and the user has permission to access device data.

• Resolution tips:

  • Verify the device Id is valid and exists in NinjaOne.
  • Confirm that the API credentials are correctly set up and have necessary scopes.
  • Use the "Include" field only with supported options like "bl" for BitLocker status.

Links and References

• NinjaOne API Documentation (general reference for API endpoints)
• BitLocker Encryption Overview (for understanding BitLocker status)