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 perform various operations on different resources. Specifically, for the Files resource with the Upload operation, it uploads binary files from previous nodes into the Lexware system. This is useful when you need to programmatically add documents or files (such as vouchers or generic files) to your Lexware account directly from an n8n workflow.
Practical examples include:
- Uploading scanned voucher documents automatically after processing them in a prior step.
- Adding generic files like PDFs or images related to invoices or contacts into Lexware for record-keeping.
Properties
| Name | Meaning |
|---|---|
| Binary Property | The name of the binary property from the previous node that contains the file data. |
| Type | The type of file being uploaded. Options: Voucher or Generic. |
Output
The node outputs JSON data representing the result of the upload operation. This typically includes metadata about the uploaded file such as its ID, status, and any relevant response information from the Lexware API.
If the node supports binary output (not explicitly shown here), it would represent the uploaded file or confirmation data in binary form, but this is not indicated in 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 service being available and accessible.
- Proper configuration of the binary property in preceding nodes is necessary to provide the file data for upload.
Troubleshooting
Common issues:
- Incorrect binary property name: If the specified binary property does not exist or is empty, the upload will fail.
- Invalid file type or unsupported file format by Lexware may cause errors.
- Authentication failures due to missing or invalid API credentials.
- Network or API downtime can prevent successful uploads.
Error messages:
- "Unsupported resource": Occurs if the resource parameter is set incorrectly; ensure it is set to "Files".
- Errors related to missing binary data: Verify the binary property name matches exactly the property from the previous node.
- API authentication errors: Check that the API key credential is correctly configured and valid.
Links and References
- Lexware Official API Documentation (example placeholder link)
- n8n documentation on working with binary data
- n8n community forums for troubleshooting API integrations