Actions41
- Articles Actions
- Contacts Actions
- Dunnings Actions
- Invoices Actions
- Order Confirmations Actions
- Quotations Actions
- Voucher Lists Actions
- Vouchers Actions
- Countries Actions
- Files Actions
Overview
The node integrates with the Lexware API to manage order confirmations among other resources. Specifically, the Update operation for Order Confirmations allows users to modify existing order confirmation records by providing the unique identifier and the updated data in JSON format.
This node is beneficial in scenarios where automated workflows need to keep order confirmation data synchronized with external systems or update details programmatically without manual intervention. For example, after receiving updated order details from a CRM or ERP system, this node can update the corresponding order confirmation in Lexware automatically.
Properties
| Name | Meaning |
|---|---|
| Order Confirmation ID | The unique identifier of the order confirmation to update. Required to specify which record to modify. |
| Order Confirmation | The raw JSON body representing the order confirmation data according to the Lexware API schema. This includes fields like title, voucher date, line items, total price, etc. |
Output
The node outputs the updated order confirmation data as JSON in the json output field. This JSON reflects the current state of the order confirmation after the update operation has been applied.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Lexware API.
- Needs an API authentication token or API key credential configured within n8n to authorize requests.
- The node depends on the Lexware API's availability and correct configuration of permissions to update order confirmations.
Troubleshooting
Common Issues:
- Providing an invalid or non-existent Order Confirmation ID will result in errors indicating that the resource could not be found.
- Malformed JSON in the "Order Confirmation" property may cause request failures due to invalid payloads.
- Insufficient API permissions or expired credentials will lead to authorization errors.
Error Messages and Resolutions:
- "Resource not found" — Verify that the Order Confirmation ID is correct and exists in Lexware.
- "Invalid JSON body" — Ensure the JSON structure matches the expected Lexware API schema.
- "Unauthorized" or "Authentication failed" — Check that the API credentials are valid and have not expired.
- Network or timeout errors — Confirm network connectivity and Lexware API service status.
Links and References
- Lexware API Documentation (Please refer to the official Lexware API docs for detailed schema and examples)
- n8n Documentation on Creating Custom Nodes