Actions41
- Articles Actions
- Contacts Actions
- Dunnings Actions
- Invoices Actions
- Order Confirmations Actions
- Quotations Actions
- Voucher Lists Actions
- Vouchers Actions
- Countries Actions
- Files Actions
Overview
This node integrates with the Lexware API to manage vouchers, specifically supporting operations such as updating voucher details. The "Update" operation for the "Vouchers" resource allows users to modify existing vouchers by specifying their ID and changing properties like title, date, contact association, and line items.
Typical use cases include automating updates to financial or accounting vouchers in Lexware from workflows, such as correcting voucher information, adding or modifying line items, or updating associated contacts and dates. For example, a user might update a voucher's title and line items after receiving additional invoice details or corrections.
Properties
| Name | Meaning |
|---|---|
| Voucher ID | The unique identifier of the voucher to update. Required to specify which voucher is being modified. |
| Title | The new title or name for the voucher. |
| Voucher Date | The date associated with the voucher, typically representing when the voucher was issued or relevant. |
| Contact ID | Identifier of the contact linked to the voucher, allowing association or reassignment. |
| Line Items | A collection of individual items within the voucher. Each item includes: |
| - Type: Specifies if the line item is custom or text. | |
| - Name: Name of the line item. | |
| - Description: Details about the line item. | |
| - Quantity: Number of units for the item. | |
| - Unit Name: Measurement unit for the quantity (e.g., pcs, hours). | |
| - Net Amount: Amount before tax and discounts. | |
| - Gross Amount: Total amount including taxes. | |
| - Tax Rate %: Percentage rate of tax applied. | |
| - Discount %: Percentage discount applied to the line item. | |
| - Line Item Amount: Final calculated amount for the line item. |
Output
The node outputs an array of JSON objects representing the updated voucher(s) after the operation completes. Each output object contains the voucher data as returned by the Lexware API, reflecting the changes made.
If the node supports binary data output (not indicated explicitly here), it would typically represent files or attachments related to vouchers, but this is not evident from the provided code and properties.
Dependencies
- Requires an active connection to the Lexware API via an API key credential configured in n8n.
- The node depends on the Lexware API endpoints for vouchers, specifically the update endpoint.
- No other external dependencies are indicated.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Voucher ID will likely result in an error from the API indicating the voucher cannot be found.
- Missing required fields such as Voucher ID will cause the node to fail before making the API call.
- Incorrectly formatted line items (e.g., missing required fields or invalid data types) may cause validation errors.
- Network or authentication issues with the Lexware API can prevent successful updates.
Error Messages:
- Errors indicating unsupported resources or operations suggest misconfiguration of the node parameters.
- API errors related to authorization imply that the API key credential is missing, expired, or invalid.
- Validation errors from the API will usually specify which field is incorrect or missing; ensure all required fields conform to expected formats.
Links and References
- Lexware Official API Documentation (Note: Replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes
- General guidance on Handling API Credentials in n8n
This summary is based solely on static analysis of the provided source code and property definitions.