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 information about device groups associated with a specific network device. This operation is useful for network administrators who want to programmatically access groupings or categorizations of devices managed within LibreNMS, enabling automation of inventory management, reporting, or configuration tasks.
For example, a user might use this node to fetch all groups that a particular device belongs to in order to generate reports on device categorization or to trigger workflows based on group membership changes.
Properties
| Name | Meaning |
|---|---|
| Device | The hostname or unique identifier of the device whose groups you want to retrieve. |
Output
The node outputs JSON data representing the groups associated with the specified device. Each item in the output corresponds to a group entity containing details such as group name, ID, and possibly other metadata defined by LibreNMS for device groups.
No binary data output is expected from this operation.
Dependencies
- Requires an active connection to a LibreNMS instance.
- Needs an API key credential configured in n8n to authenticate requests against the LibreNMS API.
- The base URL of the LibreNMS API must be set correctly in the credentials.
- Optionally, SSL certificate validation can be disabled if using self-signed certificates.
Troubleshooting
- Common issues:
- Invalid or missing device identifier will result in errors or empty results.
- Incorrect API credentials or insufficient permissions may cause authentication failures.
- Network connectivity problems between n8n and LibreNMS server can lead to request timeouts or connection errors.
- Error messages:
- Authentication errors typically indicate invalid API keys; verify and update credentials.
- "Device not found" errors suggest the provided device ID or hostname does not exist in LibreNMS; double-check the input.
- SSL errors can occur if the LibreNMS server uses a self-signed certificate and the option to allow unauthorized certs is not enabled.
Links and References
If you need further details on other operations or resources, feel free to ask!