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 providing access to billing information when using the "Bills" resource with the "Get" operation. This operation retrieves detailed data about a specific bill identified by its unique Bill ID. It is useful for scenarios where users need to fetch billing details for auditing, reporting, or integration with financial systems.
For example, a network administrator could use this node to automatically pull billing records for a particular billing cycle or customer, enabling automated invoicing or cost analysis workflows.
Properties
| Name | Meaning |
|---|---|
| Bill ID | The unique identifier of the bill to retrieve. Required to specify which bill to get. |
| Options | Additional options for the request: |
| Period | Billing period to retrieve. Possible values: "Current" (default) or "Previous". |
Output
The output JSON contains the detailed information of the requested bill as returned by the LibreNMS API. This typically includes fields such as bill amount, billing period, associated devices or services, and other metadata related to the bill.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to a LibreNMS instance.
- Needs an API key credential configured in n8n to authenticate requests.
- The base URL and SSL certificate validation settings are derived from the credential configuration.
Troubleshooting
- Missing or invalid Bill ID: The node requires a valid Bill ID. If omitted or incorrect, the API will likely return an error indicating the bill was not found.
- Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions to access billing data.
- Network connectivity issues: Verify that the LibreNMS instance URL is reachable and that SSL settings match the server's configuration.
- Invalid period option: Only "Current" or "Previous" periods are supported. Using other values may cause the API to reject the request.