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 interacts with the LibreNMS network monitoring system to create or update billing information (bills). It allows users to define billing cycles, specify bill types, associate ports, and provide additional metadata such as customer ID or notes. This is useful for automating billing management within a network monitoring context, for example, generating monthly bills based on port usage or quotas.
Practical examples:
- Creating a new bill for a customer specifying the billing day, type (CDR or Quota), and associated ports.
- Updating an existing bill by providing its Bill ID along with updated values like quota or notes.
Properties
| Name | Meaning |
|---|---|
| Bill Name | The name of the bill to be created or updated. |
| Bill Day | The day of the month when the billing cycle occurs (e.g., "1" for the first day). |
| Bill Type | The type of billing; options are: "CDR" (Call Detail Record) or "Quota". |
| Ports | Comma-separated list of port IDs associated with this bill (e.g., "1021,1022,1023"). |
| Bill ID (for update) | Identifier of an existing bill to update instead of creating a new one. |
| CDR Value | The value related to CDR type bills (used if Bill Type is "CDR"). |
| Quota | The quota value for quota type bills (used if Bill Type is "Quota"). |
| Customer ID | Identifier for the customer associated with the bill. |
| Bill Reference | A reference string for the bill, useful for tracking or external systems. |
| Notes | Additional notes or comments about the bill. |
Output
The node outputs JSON data representing the result of the create or update operation on the bill. This typically includes details of the bill record as stored or updated in LibreNMS, such as its ID, name, type, associated ports, and any other relevant metadata.
If binary data were involved (not indicated here), it would represent files or attachments related to the bill, but this node focuses on JSON structured data only.
Dependencies
- Requires connection to a LibreNMS instance via its API.
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The base URL of the LibreNMS API must be set correctly in the node credentials.
- SSL certificate validation can be optionally disabled via credential settings.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Incorrect or malformed port IDs may lead to errors or unexpected results.
- Providing a Bill ID that does not exist when updating will likely cause an error.
- Mismatched bill type and corresponding values (e.g., setting CDR value for a quota type bill) might cause logical errors or ignored fields.
Error messages:
- Authentication errors: Check API key/token validity and permissions.
- Validation errors: Ensure required fields like Bill Name, Bill Day, Bill Type, and Ports are provided and correctly formatted.
- Not found errors when updating: Verify the Bill ID exists in LibreNMS before attempting update.