Actions61
- Contact Actions
- Article Actions
- Voucher Actions
- Invoice Actions
- Down Payment Invoice Actions
- Quotation Actions
- Credit Note Actions
- Delivery Note Actions
- Dunning Actions
- File Actions
- Profile Actions
- Country Actions
- Payment Condition Actions
- Event Subscription Actions
- Recurring Template Actions
- Voucherlist Actions
- Trigger Actions
Overview
This node integrates with the Lexware Office API to manage vouchers and other related resources. Specifically, for the Voucher - Update operation, it allows users to update existing voucher records in their Lexware Office system by specifying the voucher ID and any fields they want to modify.
Common scenarios where this node is beneficial include:
- Automating updates to financial documents such as invoices or credit notes represented as vouchers.
- Synchronizing voucher data from external systems into Lexware Office.
- Adding or modifying metadata like names, descriptions, notes, tags, or external IDs on vouchers.
For example, a user might update a voucher's description and tags after receiving additional information about a transaction or correcting an earlier entry.
Properties
| Name | Meaning |
|---|---|
| Voucher ID | The unique identifier of the voucher to update (required). |
| Additional Fields | Optional collection of fields to update on the voucher: |
| - Name: Name of the voucher. | |
| - Description: Description text for the voucher. | |
| - Notes: Additional notes related to the voucher. | |
| - Tags: Comma-separated tags for categorization or filtering. | |
| - External ID: An external system identifier associated with the voucher. |
Output
The node outputs a JSON array containing the updated voucher object(s) returned from the Lexware Office API. Each item in the output corresponds to one voucher record with its updated properties.
The structure of each JSON object reflects the voucher resource schema from Lexware Office, including all standard and updated fields.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the base URL of the Lexware Office API to be configured in the credentials.
- Network connectivity to the Lexware Office API endpoint is necessary.
Troubleshooting
- Missing Required Fields Error: If required fields are not provided (e.g., Voucher ID), the node throws an error listing missing fields. Ensure all mandatory inputs are set.
- Authentication Failures: Errors related to invalid or missing API keys indicate credential misconfiguration. Verify that the API key credential is correctly set up.
- API Endpoint Issues: Connection errors may occur if the base URL is incorrect or the API service is unreachable. Confirm the API URL and network access.
- Invalid Field Values: Providing unsupported or incorrectly formatted values in additional fields may cause API errors. Validate input formats according to Lexware Office API documentation.
Links and References
- Lexware Office API Documentation (official API docs for detailed resource schemas and operations)
- n8n Documentation (for general guidance on using n8n nodes and credentials)
This summary is based solely on static analysis of the provided source code and property definitions.