Actions158
- System Actions
- Organization Actions
- Devices Actions
- Get Device
- Get Device Active Jobs
- Get Device Activities
- Get Device Alerts
- Get Device Disk Drives
- Get Device Installed OS Patches
- Get Device Installed Software Patches
- Get Device Last Logged On User
- Get Device Network Interfaces
- Get Device Pending Failed Rejected OS Patches
- Get Device Pending Failed Rejected Software Patches
- Get Device Processors
- Get Device Services
- Get Device Software
- Get Device Volumes
- Get Node Custom Fields
- Update Node Attribute Values
- Get Policy Overrides
- Groups Actions
- Queries Actions
- Get Antivirus Status Report
- Get Antivirus Threats
- Get Computer Systems
- Get Custom Fields Detailed Report
- Get Custom Fields Report
- Get Device Health Report
- Get Device Usage
- Get Disk Drives
- Get Installed OS Patches
- Get Installed Software Patches
- Get Last Logged On Users Report
- Get Network Interfaces
- Get Operating Systems
- Get Pending Failed Rejected OS Patches
- Get Pending Failed Rejected Software Patches
- Get Policy Overrides 1
- Get Processors
- Get RAID Controller Report
- Get RAID Drive Report
- Get Scoped Custom Fields Detailed Report
- Get Scoped Custom Fields Report
- Get Software
- Get Volumes
- Get Windows Services Report
- Management Actions
- Get Custom Fields Policy Conditions
- Create Custom Fields Policy Condition
- Get Windows Event Policy Conditions
- Create Windows Event Policy Condition
- Delete Policy Condition
- Get Custom Fields Policy Condition
- Get Windows Event Policy Condition
- Create Organization
- Node Approval Operation
- Reset Alert
- Reset Alert Set Activity Data
- Update Device Maintenance
- Cancel Device Maintenance
- Control Windows Service
- Update Device
- Get Device Link
- Reset Policy Overrides
- Reboot Devices
- Remove Device Owner
- Request Scripting Options
- Run Script On Device
- Set Device Owner
- Set Windows Service Configuration
- Submit OS Patch Apply
- Submit OS Patch Scan
- Submit Software Patch Apply
- Submit Software Patch Scan
- Create Location For Organization
- Get Installer
- Get Installer For Location
- Update Organization
- Update Location
- Update Node Role Policy Assignment For Organization
- Create Policy
- Ticketing Actions
- Webhooks Actions
- Related Items Actions
- Location Actions
- Backup Actions
- Knowledge Base Articles Actions
- Upload Temp Attachments
- Download Knowledge Base Article
- Get Client Knowledge Base Articles
- Get Global Knowledge Base Articles
- Get Knowledge Base Article Signed Urls
- Get Knowledge Base Folder Content
- Get Knowledge Base Folder Path Content
- Download Related Item Attachment
- Get Related Item Attachments Signed Urls
- Organization Documents Actions
- Document Templates Actions
- Checklist Templates Actions
- Custom Fields Actions
- Organization Checklists Actions
Devices → Get Device Network Interfaces
AI-generatedOverview
This node integrates with the NinjaOne API to retrieve information about devices and their network interfaces. Specifically, the "Get Device Network Interfaces" operation fetches the network interface details of a specified device by its identifier. This is useful in IT management scenarios where you need to audit or monitor device connectivity, gather IP addresses, MAC addresses, or other network-related data for inventory, troubleshooting, or compliance purposes.
Practical examples:
- Automatically retrieving all network interfaces of a device before performing remote management tasks.
- Collecting network interface data for asset tracking or reporting.
- Integrating device network info into a CMDB (Configuration Management Database).
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the device whose network interfaces you want to retrieve. This is a required input. |
Output
The node outputs an array of JSON objects, each representing the response from the NinjaOne API for the requested device's network interfaces. The json field contains the detailed network interface data as returned by the API, which typically includes properties such as interface names, IP addresses, MAC addresses, status, and other relevant network details.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 authentication credential configured in n8n.
- The node uses the NinjaOne REST API endpoints under
/v2/devices/{id}/network-interfaces(inferred from the operation context). - Proper API permissions are needed to access device network interface information.
Troubleshooting
- Missing or invalid device Id: Ensure that the "Id" property is provided and corresponds to a valid device in NinjaOne.
- Authentication errors: Verify that the NinjaOne API credentials are correctly set up and have not expired.
- API rate limits or permission issues: Check NinjaOne account permissions and API usage limits.
- No network interfaces returned: Confirm that the device has network interfaces configured and accessible via the API.
Common error messages may include:
"No binary data exists on item!"or"No binary data property ... does not exist"— these do not apply to this operation since it does not handle binary data.- API errors returned from NinjaOne will be passed through; check the error message for details such as unauthorized access, resource not found, or bad request.
Links and References
- NinjaOne API Documentation (general reference for API endpoints)
- n8n Documentation - Creating Custom Nodes
- OAuth2 Authentication setup in n8n (for connecting NinjaOne API)