NinjaOne icon

NinjaOne

Interact with the NinjaOne API
Join our community

Actions30

Overview

The node interacts with the NinjaOne API to retrieve information about devices and their associated data. Specifically, for the "Device" resource and the "Get Volumes" operation, it fetches volume details of a specified device by its ID. This is useful in IT management scenarios where you need to monitor or audit storage volumes on managed devices.

Practical examples include:

  • Retrieving disk volume information to check available space or volume health.
  • Integrating device volume data into asset management or reporting workflows.
  • Automating alerts or actions based on volume status or capacity.

Properties

Name Meaning
Device ID ID of the device whose volumes are to be retrieved (string, required)

Output

The node outputs JSON data containing the volume information of the specified device. The structure typically includes details such as volume names, sizes, free space, file system types, and other relevant volume attributes as returned by the NinjaOne API.

If the node supports binary data output (not explicitly shown here), it would represent files or attachments related to the device volumes, but this operation primarily returns JSON volume metadata.

Dependencies

  • Requires an active connection to the NinjaOne API.
  • Needs an API authentication token configured via OAuth2 credentials within n8n.
  • The base URL for the API can be customized but defaults to https://api.ninjaone.com.

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 credentials are valid and have sufficient permissions to access device volume data.
  • API Rate Limits: Frequent requests may hit rate limits imposed by NinjaOne; consider adding delays or handling retries.
  • Network Issues: Connectivity problems between n8n and the NinjaOne API endpoint can cause failures; verify network access.

Common error messages might include unauthorized access, resource not found, or bad request errors. Resolving these usually involves checking credentials, input parameters, and API availability.

Links and References

Discussion