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
Queries → Get Network Interfaces
AI-generatedOverview
This node interacts with the NinjaOne API to retrieve network interface information based on specified query parameters. It is useful for IT administrators or automation engineers who want to programmatically fetch details about network interfaces from devices managed by NinjaOne. For example, you can filter network interfaces by device name, paginate through results using a cursor, or limit the number of returned devices.
Properties
| Name | Meaning |
|---|---|
| Df | Device filter: Filter network interfaces by device identifier or name (string). |
| Cursor | Cursor name: Used for pagination to specify the position in the result set (string). |
| Page Size | Limit number of devices to return: Controls how many network interface records are fetched (number). |
Output
The output is an array of JSON objects representing the network interfaces retrieved from the NinjaOne API. Each item contains detailed information about a network interface as returned by the API. The exact structure depends on the NinjaOne API response but typically includes fields such as interface name, status, IP addresses, MAC address, and related device info.
No binary data output is produced by this operation.
Dependencies
- Requires an active NinjaOne API OAuth2 credential configured in n8n.
- Depends on the NinjaOne API being accessible and the user having appropriate permissions to query network interfaces.
- Uses the built-in HTTP request helper with authentication to communicate with the NinjaOne API.
Troubleshooting
- Common issues:
- Invalid or expired API credentials will cause authentication failures.
- Incorrect device filter values may result in empty responses.
- Pagination cursors that are outdated or invalid may cause errors or no results.
- Error messages:
- Errors from the NinjaOne API will be returned in the
json.errorfield if "Continue On Fail" is enabled. - Typical errors include authorization errors, invalid parameters, or rate limiting.
- Errors from the NinjaOne API will be returned in the
- Resolutions:
- Verify and refresh API credentials.
- Double-check filter values and pagination parameters.
- Handle API rate limits by adding delays or retries.
Links and References
- NinjaOne API Documentation (for detailed API endpoint and parameter info)
- n8n Documentation (for general usage of HTTP Request nodes and credentials)