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 "Add Devices" operation under the "Device Groups" resource enables users to add one or more devices to an existing device group by specifying the group name and a list of device IDs.
This operation is useful in scenarios where network administrators want to organize devices into logical groups for easier monitoring, alerting, or reporting within LibreNMS. For example, adding newly provisioned devices to a specific group representing a data center or department can streamline management tasks.
Properties
| Name | Meaning |
|---|---|
| Group Name | The name of the device group to which devices will be added. |
| Devices | A comma-separated list of device IDs to add to the specified device group (e.g., "1,2,3"). |
Output
The node outputs JSON data representing the result of the add devices operation. This typically includes confirmation of the devices added to the group or any relevant status messages returned by the LibreNMS API. The exact structure depends on the API response but generally confirms success or details errors.
No binary data output is involved in this operation.
Dependencies
- Requires connection to a LibreNMS instance via its REST API.
- Needs an API authentication token configured in the node credentials to authorize requests.
- 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
- Invalid Group Name: If the specified device group does not exist, the API may return an error indicating the group was not found. Verify the group name spelling and existence.
- Invalid Device IDs: Providing device IDs that do not exist or are not accessible may cause partial or complete failure. Ensure device IDs are correct and belong to the LibreNMS instance.
- Authentication Errors: Missing or incorrect API tokens will lead to authorization failures. Confirm that the API key credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems between n8n and LibreNMS server can cause timeouts or connection errors. Check network access and firewall settings.
- Malformed Input: The devices property must be a comma-separated string of numeric IDs without extra spaces or invalid characters.