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 interacts with the LibreNMS network monitoring system, specifically allowing management of device groups. The "Update" operation for Device Groups enables users to modify existing device group details such as the group's name and description. This is useful in scenarios where network administrators need to reorganize or rename device groups to reflect changes in network topology or administrative policies.
Practical examples include:
- Renaming a device group to better represent its purpose or location.
- Adding or updating a description to provide more context about the devices contained within the group.
Properties
| Name | Meaning |
|---|---|
| Group Name | The name of the device group to update. This is required to identify which group to modify. |
| Additional Options | Optional fields for the update operation. Currently supports: - Description: A textual description of the device group. |
Output
The node outputs JSON data representing the result of the update operation on the device group. This typically includes confirmation of the updated group details such as the new name and description, or any status messages returned by the LibreNMS API.
If the node supports binary data output (not indicated here), it would generally relate to files or attachments associated with device groups, but this is not applicable for the update operation.
Dependencies
- Requires an active connection to a LibreNMS instance via its API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the node's credential configuration.
- SSL certificate validation can be optionally disabled if using self-signed certificates.
Troubleshooting
Common Issues:
- Incorrect or missing group name will cause the update to fail since the target group cannot be identified.
- Invalid or expired API credentials will prevent successful communication with LibreNMS.
- Network connectivity issues between n8n and the LibreNMS server can cause timeouts or errors.
Error Messages:
- "Group not found" — Verify that the specified group name exists in LibreNMS.
- "Unauthorized" or "Authentication failed" — Check API credentials and permissions.
- "Invalid input" — Ensure all required fields are provided and valid, especially the group name.
Resolving these usually involves verifying the input parameters, checking API credentials, and ensuring network access to the LibreNMS server.