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 under the "Bills" resource. The "Get History" operation retrieves the historical data related to a specific bill identified by its Bill ID. This is useful for users who want to track past billing records, audit charges over time, or analyze billing trends within their network monitoring environment.
Practical examples include:
- Fetching detailed billing history for a particular invoice to verify charges.
- Automating reports on billing changes or updates for accounting purposes.
- Integrating billing history data into broader network management dashboards.
Properties
| Name | Meaning |
|---|---|
| Bill ID | The unique identifier of the bill whose history you want to retrieve. This is a required string input. |
Output
The node outputs JSON data containing the historical details of the specified bill. This typically includes timestamps, amounts, status changes, and other relevant billing events associated with that bill. The exact structure depends on the LibreNMS API response but generally provides a chronological record of billing activity.
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 against the LibreNMS API.
- The base URL and SSL certificate validation settings are configurable via credentials.
Troubleshooting
- Common issues:
- Invalid or missing Bill ID will cause the operation to fail; ensure the Bill ID is correct and provided.
- Authentication errors if the API key credential is incorrect or lacks necessary permissions.
- Network connectivity problems between n8n and the LibreNMS server.
- Error messages:
- "Unauthorized" or "Authentication failed": Check API key validity and permissions.
- "Bill not found": Verify the Bill ID exists in LibreNMS.
- SSL errors: If using self-signed certificates, enable the option to allow unauthorized certificates in credentials.
Links and References
Note: This summary is based solely on static analysis of the provided source code and property definitions.