LibreNMS icon

LibreNMS

Interact with LibreNMS network monitoring system
Join our community

Actions83

Overview

The node enables creating device groups within the LibreNMS network monitoring system. Device groups help organize and manage sets of devices either statically by specifying exact device IDs or dynamically by defining rules that automatically include devices matching certain criteria.

This node is useful in scenarios such as:

  • Grouping devices for bulk operations, monitoring, or reporting.
  • Creating dynamic groups that update automatically based on device attributes (e.g., status).
  • Organizing devices by location, type, or operational state without manual updates.

For example, a user can create a static group named "Core Switches" including specific device IDs, or a dynamic group named "Active Devices" that includes all devices with status equal to 1.

Properties

Name Meaning
Group Name The name assigned to the device group.
Group Type The type of device group:
- Static: Manually specify device IDs.
- Dynamic: Define rules to select devices automatically.
Devices (Static groups only) Comma-separated list of device IDs to include in the group.
Rules (Dynamic groups only) JSON object defining conditions and rules to select devices dynamically.
Additional Options Optional extra settings:
- Description: Text description of the device group.

Output

The node outputs JSON data representing the created device group. This typically includes details such as the group's ID, name, type, included devices or rules, and any additional metadata like description.

No binary data output is involved.

Dependencies

  • Requires connection to a LibreNMS instance via its API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • The base URL of the LibreNMS API must be set correctly in the node's credentials.
  • SSL certificate validation can be optionally disabled if using self-signed certificates.

Troubleshooting

  • Invalid Device IDs: When creating a static group, ensure device IDs are valid and exist in LibreNMS; otherwise, the API may reject the request.
  • Malformed Rules JSON: For dynamic groups, the rules property must be valid JSON following LibreNMS rule schema; invalid JSON will cause errors.
  • Authentication Errors: Verify that the API key/token is correct and has sufficient permissions.
  • API Endpoint Issues: Confirm the LibreNMS API base URL is correct and accessible from n8n.
  • SSL Certificate Problems: If using self-signed certificates, enable the option to skip SSL validation or provide proper certificates.

Common error messages usually relate to authorization failures, invalid input data, or connectivity issues. Reviewing the API response message helps identify the root cause.

Links and References

Discussion