NinjaOne icon

NinjaOne

Interact with the NinjaOne API
Join our community

Actions30

Overview

The node integrates with the NinjaOne API to retrieve detailed information about device processors. Specifically, the "Get Processors" operation under the "Device" resource fetches processor details for a specified device by its ID. This is useful in IT asset management, monitoring hardware specifications, or automating inventory updates.

Practical examples include:

  • Automatically gathering processor information of devices in an organization to maintain an up-to-date hardware inventory.
  • Triggering workflows based on processor types or counts, such as provisioning software compatible with certain CPU architectures.
  • Auditing devices for compliance or performance analysis by extracting processor details.

Properties

Name Meaning
Device ID The unique identifier of the device whose processor information you want to retrieve. This is a required string input.

Output

The node outputs JSON data containing the processor details of the specified device. The exact structure depends on the NinjaOne API response but typically includes fields such as processor model, speed, core count, and other relevant hardware attributes.

No binary data output is indicated for this operation.

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 defaults to https://api.ninjaone.com but can be overridden by credential settings.

Troubleshooting

  • Common Issues:

    • Invalid or missing Device ID will cause the request to fail.
    • Authentication errors if the API token is expired or misconfigured.
    • Network connectivity issues preventing access to the NinjaOne API endpoint.

  • Error Messages:

    • Unauthorized or 401 errors indicate problems with API credentials; verify and refresh tokens as needed.
    • 404 Not Found may mean the device ID does not exist or is incorrect.
    • Rate limiting or 429 errors require waiting or adjusting API usage.

Resolving these usually involves checking the provided Device ID, ensuring valid API credentials, and confirming network access.

Links and References

  • NinjaOne API Documentation (for detailed API endpoints and data structures)
  • n8n OAuth2 Credential Setup Guide (within n8n documentation)

Discussion