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 to retrieve billing information associated with customers. Specifically, the "Get by Customer ID" operation fetches bills for a given customer based on their unique identifier. This is useful in scenarios where you want to automate retrieval of billing data for invoicing, auditing, or reporting purposes within your network management workflows.
For example, you could use this node to:
- Automatically pull the latest bill for a specific customer to include in a monthly report.
- Retrieve previous billing periods for comparison or trend analysis.
- Integrate billing data into a CRM or accounting system.
Properties
| Name | Meaning |
|---|---|
| Customer ID | The unique identifier of the customer whose bills you want to retrieve. |
| Options | Additional parameters to customize the request: |
| Period | Select the billing period to retrieve. Options are "Current" (default) or "Previous". |
Output
The node outputs JSON data representing the billing information retrieved from LibreNMS for the specified customer. The structure typically includes details such as billing amounts, dates, and related metadata depending on the LibreNMS API response.
If binary data were involved (e.g., PDF invoices), it would be indicated here, but this operation returns structured JSON billing data only.
Dependencies
- Requires an active connection to a LibreNMS instance via its API.
- An API key credential must be configured in n8n to authenticate requests.
- The LibreNMS API base URL and SSL certificate validation settings are configured through credentials.
Troubleshooting
- Missing or invalid Customer ID: Ensure the Customer ID property is provided and correctly matches an existing customer in LibreNMS.
- API authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network connectivity issues: Confirm that the LibreNMS server URL is reachable from the n8n environment.
- Invalid period option: Use only the supported values ("Current" or "Previous") for the billing period.
- Unexpected API responses: Check LibreNMS logs and API documentation if the returned data does not match expectations.
Links and References
- LibreNMS Official Website
- LibreNMS API Documentation
- n8n Documentation - HTTP Request Node (for understanding API calls)