Actions30
- Device Actions
- Ticket Actions
- Organization Actions
- Document Actions
Overview
The node interacts with the NinjaOne API to retrieve software information installed on a specific device. It is designed to fetch detailed software data for a given device ID, which can be useful in IT asset management, software inventory tracking, or compliance auditing scenarios. For example, an IT administrator could use this node to automatically gather and update the list of installed software across multiple devices in their network.
Properties
| Name | Meaning |
|---|---|
| Device ID | ID of the device to query software information from |
Output
The node outputs JSON data containing the software details associated with the specified device. The exact structure depends on the NinjaOne API response but typically includes software names, versions, installation dates, and other relevant metadata.
If the node supports binary data output (not explicitly shown here), it would represent files or attachments related to the software information, but this is not indicated in the provided code.
Dependencies
- Requires an API key credential for authenticating with the NinjaOne API.
- The base URL for the API defaults to
https://api.ninjaone.combut can be overridden by credentials. - The node depends on the NinjaOne API being accessible and the provided device ID being valid.
Troubleshooting
- Invalid Device ID: If the device ID is incorrect or does not exist, the node may return an error or empty results. Verify the device ID before running.
- Authentication Errors: Ensure that the API key credential is correctly configured and has sufficient permissions.
- API Rate Limits: The NinjaOne API may enforce rate limits; if exceeded, requests might fail temporarily.
- Network Issues: Connectivity problems between n8n and the NinjaOne API endpoint can cause failures.
Links and References
- NinjaOne API Documentation (general reference for API endpoints and data structures)