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 create various types of vouchers. Specifically, for the "Voucher" resource and the "Create" operation, it allows users to generate a new voucher document of a specified type such as invoice, credit note, or delivery note.
Common scenarios where this node is beneficial include automating financial document creation in accounting workflows, generating sales or purchase invoices programmatically, or creating order confirmations and quotations within an automated business process.
For example, a user can automate the creation of a sales invoice voucher after a successful sale transaction in their e-commerce system, or generate a purchase credit note voucher when processing supplier returns.
Properties
| Name | Meaning |
|---|---|
| Voucher Type | The type of voucher to create. Options include: Sales Invoice, Sales Credit Note, Purchase Invoice, Purchase Credit Note, Invoice, Down Payment Invoice, Credit Note, Order Confirmation, Quotation, Delivery Note. |
| Additional Fields | Optional additional fields to set on the voucher, including: |
| - Name: Name of the voucher resource | |
| - Description: Description of the voucher | |
| - Notes: Additional notes | |
| - Tags: Tags associated with the voucher | |
| - External ID: External identifier for the voucher |
Output
The node outputs an array of JSON objects representing the created voucher(s). Each object contains the details of the newly created voucher as returned by the Lexware Office API. This typically includes identifiers, status, type, and any other metadata related to the voucher.
The node does not output binary data for 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.
- No other external dependencies are required.
Troubleshooting
- Missing Required Fields Error: If required fields for the voucher creation are missing, the node throws an error listing the missing fields. Ensure all mandatory properties, especially "Voucher Type", are provided.
- Authentication Errors: If the API key or resource URL is incorrect or missing, authentication will fail. Verify that the API key credential is correctly configured.
- API Rate Limits: The Lexware Office API may enforce rate limits. If requests are throttled, consider adjusting the workflow to reduce request frequency.
- Invalid Voucher Type: Providing an unsupported voucher type value will cause errors. Use one of the predefined voucher type options.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)
If you need further details about other operations or resources, feel free to ask!