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, specifically providing functionality to retrieve a list of network devices. The "Get All" operation under the "Devices" resource fetches multiple devices from LibreNMS based on various filtering and sorting criteria.
This node is useful in scenarios where you want to automate network inventory management, monitor device statuses, or integrate device data into other workflows. For example, you could use it to regularly pull active devices for reporting, or to trigger alerts when certain devices go down.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of filters and options to refine the list of devices returned: |
| - Type | Filter devices by status. Options: All, Active, Ignored, Up, Down, Disabled |
| - Order | Specify ordering of results using a string (e.g., "hostname DESC") |
| - Query | Search term to filter devices by hostname, IP, or other fields |
| - Sort | Sort order for results. Options: Ascending, Descending |
| - Limit | Maximum number of devices to return |
| - Offset | Number of devices to skip (useful for pagination) |
Output
The node outputs JSON data representing an array of devices matching the specified filters. Each device object typically includes details such as hostname, IP address, status, and other device-specific information as provided by LibreNMS.
If binary data were involved (not indicated here), it would be summarized accordingly, but this operation returns structured JSON data only.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API key credential configured in n8n for authentication.
- The base URL and SSL certificate validation settings are configurable through credentials.
- No additional external dependencies beyond the LibreNMS API.
Troubleshooting
Common Issues:
- Incorrect API URL or credentials will cause authentication failures.
- Using unsupported filter values may result in empty responses or errors.
- Pagination parameters (limit and offset) must be used carefully to avoid missing data.
Error Messages:
- Authentication errors usually indicate invalid or missing API keys.
- HTTP errors like 404 or 500 suggest issues with the LibreNMS server or endpoint.
- Validation errors may occur if query parameters are malformed.
Resolutions:
- Verify API credentials and URL configuration.
- Check LibreNMS API documentation for valid filter and query syntax.
- Use smaller limits and adjust offsets properly for large datasets.
Links and References
This summary is based solely on static analysis of the provided source code and property definitions.