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 operations related to network devices. The "Discover" operation under the "Devices" resource allows users to initiate a discovery process for a specified device by its hostname or ID. This is useful in scenarios where you want to update LibreNMS with the latest information about a device on your network, such as after adding new hardware or changing device configurations.
Practical examples include:
- Automatically triggering device discovery after provisioning new network equipment.
- Refreshing device data to ensure monitoring accuracy.
- Integrating with automation workflows that maintain up-to-date network inventories.
Properties
| Name | Meaning |
|---|---|
| Device | Device hostname or ID to discover (string). This identifies which device LibreNMS should perform discovery on. |
Output
The node outputs JSON data representing the result of the discovery operation for the specified device. This typically includes status information about the discovery process and any updated device details returned by LibreNMS.
If the node supports binary data output, it would relate to device-related files or logs, but based on the provided code and context, the primary output is JSON structured data.
Dependencies
- Requires an API key credential to authenticate with the LibreNMS API.
- Needs the LibreNMS instance URL configured in the credentials.
- The node uses the LibreNMS REST API v0 endpoint.
- SSL certificate validation can be optionally skipped based on credential settings.
Troubleshooting
Common issues:
- Invalid or missing device identifier will cause the discovery operation to fail.
- Network connectivity problems between n8n and LibreNMS server.
- Authentication errors due to incorrect or expired API keys.
- SSL certificate errors if the LibreNMS server uses self-signed certificates and skipping validation is not enabled.
Error messages:
- "Device not found" — Verify the device hostname or ID is correct and exists in LibreNMS.
- "Unauthorized" or "Authentication failed" — Check API key validity and permissions.
- "Network error" or "Timeout" — Ensure LibreNMS server is reachable from n8n.
Resolving these usually involves verifying input parameters, checking credentials, and ensuring network access.
Links and References
Note: The summary is based solely on static analysis of the provided source code and property definitions.