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 perform various operations on different resources, including Order Confirmations. Specifically, for the "Order Confirmations" resource and the "Get" operation, the node retrieves detailed information about a specific order confirmation by its unique identifier. This is useful in scenarios where you need to fetch and process order confirmation data within an automated workflow, such as verifying order details before further processing or generating reports.
Practical examples:
- Automatically retrieving order confirmation details after an order is placed to update internal systems.
- Fetching order confirmation data to trigger notifications or follow-up actions.
- Integrating order confirmation information into accounting or CRM systems.
Properties
| Name | Meaning |
|---|---|
| Order Confirmation ID | The unique identifier of the order confirmation to retrieve. This is a required string. |
Output
The node outputs JSON data representing the retrieved order confirmation details from the Lexware API. The structure typically includes all relevant fields describing the order confirmation, such as customer info, items, totals, dates, and status.
If the node supports binary data output (not indicated here), it would represent associated files or documents related to the order confirmation, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Lexware API via an API key credential configured in n8n.
- The node depends on the Lexware API being accessible and the credentials having sufficient permissions to read order confirmations.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing Order Confirmation ID will cause the API call to fail.
- Network connectivity problems or incorrect API credentials can prevent successful retrieval.
- If the specified order confirmation does not exist, the API may return an error or empty result.
Error messages:
- Errors indicating unsupported resource suggest misconfiguration of the resource parameter.
- Authentication errors imply invalid or expired API credentials.
- Not found errors mean the given Order Confirmation ID does not correspond to any existing record.
Resolutions:
- Verify that the Order Confirmation ID is correct and exists in Lexware.
- Ensure API credentials are valid and have necessary permissions.
- Check network connectivity and Lexware API status.
Links and References
- Lexware API Documentation (example placeholder, replace with actual URL if known)
- n8n documentation on creating custom nodes