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, enabling users to interact with various Lexware resources. Specifically, for the Files - Download operation, it allows downloading files stored in Lexware by specifying a file identifier. This is useful when automating workflows that require retrieving documents or attachments from Lexware, such as invoices, reports, or other business-related files.
Practical examples include:
- Automatically downloading invoice PDFs after they are generated in Lexware.
- Retrieving contract documents or order confirmations for further processing or archival.
- Integrating downloaded files into other systems or sending them via email.
Properties
| Name | Meaning |
|---|---|
| File ID | The unique identifier of the file to download from Lexware. |
| Binary Property | The name of the binary property where the downloaded file data will be stored in output. |
Output
The node outputs the downloaded file data in the specified binary property (default name: data). The output JSON will typically contain metadata about the file along with the binary content under the chosen binary property name. This binary data can then be used downstream in the workflow, for example, to save the file locally, upload it elsewhere, or send it as an email attachment.
Dependencies
- Requires an active connection to the Lexware API using an API key or authentication token configured in n8n credentials.
- Network access to the Lexware service endpoint.
- Proper permissions on the Lexware account to access and download files.
Troubleshooting
- File not found or invalid File ID: Ensure the provided File ID exists and is accessible with your Lexware account.
- Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
- Network issues: Check connectivity to the Lexware API endpoint.
- Binary property conflicts: Make sure the binary property name does not conflict with existing properties in the workflow to avoid overwriting data.
Links and References
- Lexware Official API Documentation (example placeholder, replace with actual URL if available)
- n8n documentation on Working with Binary Data