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 allowing management of device groups. The "Delete" operation under the "Device Groups" resource enables users to remove an existing device group by specifying its name. This is useful for network administrators who want to clean up or reorganize their device groupings within LibreNMS.
Practical examples include:
- Removing obsolete or deprecated device groups that are no longer relevant.
- Automating cleanup tasks in network monitoring workflows.
- Managing device group lifecycle as part of network infrastructure changes.
Properties
| Name | Meaning |
|---|---|
| Group Name | The name of the device group to delete. This must be an existing group in LibreNMS. |
Output
The output JSON typically contains the response from the LibreNMS API after attempting to delete the specified device group. This may include confirmation of deletion or error details if the operation failed.
No binary data output is expected from this operation.
Dependencies
- Requires an API key credential for authenticating with the LibreNMS API.
- The node expects the LibreNMS base URL and authentication credentials to be configured in n8n.
- Network connectivity to the LibreNMS instance is necessary.
Troubleshooting
Common issues:
- Specifying a non-existent group name will likely result in an error from the API indicating the group was not found.
- Authentication failures due to invalid or missing API credentials.
- Network errors if the LibreNMS server is unreachable.
Error messages and resolutions:
- "Group not found" — Verify the exact spelling and existence of the device group in LibreNMS.
- Authentication errors — Check that the API key credential is correctly set up and has sufficient permissions.
- Network timeout or connection refused — Ensure the LibreNMS server URL is correct and accessible from the n8n environment.