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
This node interacts with the LibreNMS network monitoring system, specifically allowing users to retrieve ports associated with a given port group. The "Get Ports by Group" operation under the "Port Groups" resource fetches all ports that belong to a specified port group by its name.
This is useful in scenarios where network administrators want to quickly list or analyze all ports grouped logically within LibreNMS, for example, to audit port usage, monitor traffic, or configure devices based on port grouping.
Practical examples:
- Retrieve all port IDs in a specific port group to feed into another workflow step for monitoring or alerting.
- Fetch full port details (not just IDs) for detailed reporting or integration with other systems.
Properties
| Name | Meaning |
|---|---|
| Group Name | The name of the port group whose ports you want to retrieve. |
| Options | Additional options for the request: |
| Full Data | Boolean option to return complete port data instead of just port IDs. |
Output
The output JSON contains the list of ports belonging to the specified port group. Depending on the "Full Data" option:
- If
Full Datais false (default), the output includes only the port IDs. - If
Full Datais true, the output includes comprehensive information about each port.
If the node supports binary data output, it would typically represent any associated files or attachments related to ports, but this operation primarily returns JSON data about ports.
Dependencies
- Requires an active connection to a LibreNMS instance via an API key credential.
- The node expects the LibreNMS API URL and authentication token configured in the credentials.
- The LibreNMS API must be accessible from the n8n environment.
Troubleshooting
Common issues:
- Incorrect or misspelled port group name will result in no ports found or an error.
- Network connectivity problems between n8n and LibreNMS API.
- Insufficient permissions or invalid API key may cause authorization errors.
Error messages:
- "404 Not Found" or empty results: Verify the port group name exists in LibreNMS.
- "401 Unauthorized": Check API key validity and permissions.
- "Network Error": Ensure LibreNMS API URL is correct and reachable.
Resolving these usually involves verifying input parameters, checking credentials, and ensuring network access.