NinjaOneInstall

Overview

This node integrates with the NinjaOne API to perform various operations on different resources. Specifically, for the Devices resource and the Get Device operation, it retrieves detailed information about a single device identified by its unique ID. This is useful in scenarios where you need to fetch device details such as status, configuration, or inventory data within an automated workflow.

Practical examples include:

• Automatically retrieving device information when a new ticket is created in a helpdesk system.
• Enriching asset management records with up-to-date device details.
• Triggering alerts or actions based on specific device attributes fetched dynamically.

Properties

Output

The node outputs a JSON object containing the full response from the NinjaOne API for the requested device. This typically includes all available device details such as hardware specifications, software installed, status, last check-in time, and other metadata.

If the node supports binary data (not applicable for this operation), it would provide binary content accordingly, but for "Get Device" the output is purely JSON.

Example output structure (simplified):

{
  "id": 123,
  "name": "Device Name",
  "status": "Online",
  "lastCheckIn": "2024-06-01T12:00:00Z",
  "hardware": {
    "cpu": "Intel i7",
    "ram": "16GB"
  },
  "software": [
    "App1",
    "App2"
  ],
  ...
}

Dependencies

• Requires an active connection to the NinjaOne API using OAuth2 authentication.
• The node expects the user to configure the NinjaOne API credentials in n8n beforehand.
• Network access to the NinjaOne API endpoint is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing device ID: Ensure the "Id" property is set and corresponds to an existing device.
  • Authentication errors: Verify that the NinjaOne API credentials are correctly configured and have not expired.
  • Network connectivity problems: Confirm that the n8n instance can reach the NinjaOne API servers.

• Error messages:

  • "No binary data exists on item!" or "No binary data property ... does not exist on item!" — Not relevant for this operation but may appear if other operations expecting binary input are used incorrectly.
  • API errors returned from NinjaOne will be passed through; check the error message for details like "Device not found" or "Unauthorized".

Links and References

• NinjaOne API Documentation (general reference for endpoints and data structures)
• n8n OAuth2 Credential Setup (for configuring NinjaOne API credentials)