Actions83
- Bills Actions
- Alerts Actions
- Alert Rules Actions
- ARP Actions
- Devices Actions
- Device Groups Actions
- Inventory Actions
- Locations Actions
- Logs Actions
- Poller Groups Actions
- Ports Actions
- Port Groups Actions
- Routing Actions
- Services Actions
- Switching Actions
Overview
The node integrates with the LibreNMS network monitoring system to retrieve inventory information about network devices. Specifically, the "Get Inventory" operation fetches detailed hardware inventory data for a specified device, such as chassis, modules, ports, power supplies, fans, sensors, and other physical components.
This node is beneficial in scenarios where network administrators need to audit or monitor the physical components of their network devices programmatically. For example, it can be used to automate asset management, verify hardware configurations, or trigger alerts if certain components are missing or malfunctioning.
Practical examples:
- Automatically retrieving all port modules installed on a specific switch.
- Filtering inventory to list only power supplies or fans for maintenance scheduling.
- Integrating with IT asset databases to keep hardware records up to date.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique ID of the device whose inventory you want to retrieve. |
| Filters | Optional filters to narrow down the inventory results: |
| Physical Class | Filter by type of physical component. Options include: Chassis, Backplane, Container, Power Supply, Fan, Sensor, Module, Port, Stack, Other, Unknown. |
| Physical Contained In | Filter by parent component index (e.g., to get components contained within a specific chassis or module). |
Output
The node outputs JSON data representing the inventory items matching the query parameters. Each item typically includes details about the physical component such as its class, description, identifiers, and hierarchical relationships.
If binary data were involved (e.g., images or firmware blobs), it would be indicated here, but this operation focuses on structured JSON inventory data only.
Dependencies
- Requires connection to a LibreNMS instance with API access enabled.
- Needs an API authentication token configured in n8n credentials to authorize requests.
- The base URL of the LibreNMS API must be correctly set in the credential configuration.
- Optionally, SSL certificate validation can be disabled if using self-signed certificates.
Troubleshooting
Common issues:
- Invalid or missing device identifier will result in no data or errors.
- Incorrect API credentials or insufficient permissions cause authentication failures.
- Network connectivity problems between n8n and LibreNMS server.
- Using filters with invalid values may return empty results.
Error messages:
- Authentication errors: Check API token validity and credential setup.
- 404 Not Found: Verify the device ID/hostname exists in LibreNMS.
- Timeout or network errors: Ensure LibreNMS server is reachable from n8n.
- Validation errors on filters: Confirm filter values match allowed options.