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 various business-related resources such as articles, contacts, invoices, and order confirmations. Specifically, for the Order Confirmations - Create operation, it allows users to create new order confirmation records in Lexware by sending structured JSON data that represents the order confirmation details.
Typical use cases include automating the creation of order confirmations after an order is finalized in an e-commerce system or ERP workflow, ensuring that order confirmations are consistently formatted and stored within Lexware without manual entry.
For example, after a customer places an order, this node can be used to send the order details (line items, total price, voucher date, etc.) directly to Lexware to generate an official order confirmation document.
Properties
| Name | Meaning |
|---|---|
| Order Confirmation | Raw JSON body representing the order confirmation according to the Lexware API specification. It includes fields like title, voucherDate, lineItems (array), and totalPrice (object). This property expects a JSON object describing the full order confirmation to be created. |
Output
The node outputs an array of JSON objects corresponding to the results returned from the Lexware API after creating the order confirmation(s). Each output item typically contains the details of the created order confirmation, including any identifiers assigned by Lexware and status information.
If the node supports binary data output (not explicitly shown here), it would represent related files or documents generated by Lexware (e.g., PDF versions of the order confirmation), but this is not indicated in the provided code snippet.
Dependencies
- Requires an active connection to the Lexware API via an API key or authentication token configured in n8n credentials.
- The node depends on the Lexware API being accessible and properly configured to accept order confirmation data.
- No additional external libraries beyond those bundled with the node are required.
Troubleshooting
Common issues:
- Invalid or incomplete JSON structure in the "Order Confirmation" input may cause API errors.
- Network connectivity problems or incorrect API credentials will prevent successful communication with Lexware.
- Unsupported resource or operation errors if the resource or operation parameters are misconfigured.
Error messages:
"Unsupported resource: orderConfirmations"— indicates a mismatch in resource naming; ensure the resource parameter is set correctly.- API response errors related to validation failures usually indicate missing required fields or invalid data formats in the JSON body.
Resolutions:
- Validate the JSON input against the Lexware API schema before execution.
- Verify API credentials and network access.
- Use the node’s dropdowns for resource and operation selection to avoid typos.
Links and References
- Lexware API Documentation (example placeholder, replace with actual URL)
- n8n documentation on creating custom nodes
- JSON schema guidelines for Lexware order confirmations (refer to Lexware API docs)