Actions61
- Contact Actions
- Article Actions
- Voucher Actions
- Invoice Actions
- Down Payment Invoice Actions
- Quotation Actions
- Credit Note Actions
- Delivery Note Actions
- Dunning Actions
- File Actions
- Profile Actions
- Country Actions
- Payment Condition Actions
- Event Subscription Actions
- Recurring Template Actions
- Voucherlist Actions
- Trigger Actions
Overview
The Lexware Office node integrates with the Lexware Office API, enabling users to manage various business resources such as contacts, invoices, articles, and dunnings. Specifically, for the Dunning resource with the Download File operation, this node allows users to download a specific file associated with a dunning (a reminder or collection notice related to unpaid invoices).
This operation is useful in scenarios where you need to programmatically retrieve dunning documents or related files from Lexware Office for further processing, archiving, or sending via other communication channels.
Practical example:
You have an automated workflow that triggers when a dunning is finalized, and you want to download the corresponding PDF file of the dunning notice to attach it to an email sent to the customer.
Properties
| Name | Meaning |
|---|---|
| Dunning ID | The unique identifier of the dunning from which the file will be downloaded. |
| File ID | The unique identifier of the specific file associated with the dunning to download. |
These properties are required inputs for the "Download File" operation on the "Dunning" resource.
Output
- The node outputs the downloaded file data related to the specified dunning.
- The output includes a
jsonfield containing metadata about the file or the response. - If the file is binary (e.g., PDF), the node will provide the file content in the binary output format, allowing subsequent nodes to handle or save the file accordingly.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the Lexware Office API base URL and API key to be configured in the credentials.
- No additional external dependencies are needed beyond the Lexware Office API access.
Troubleshooting
Missing Required Fields Error:
If either the Dunning ID or File ID is not provided, the node will throw an error indicating missing required fields. Ensure both IDs are correctly set.Authentication Errors:
If the API key credential is invalid or missing, the node will fail to authenticate. Verify that the API key and base URL are correctly configured in the credentials.File Not Found or Access Denied:
If the specified file ID does not exist for the given dunning or if permissions are insufficient, the API may return an error. Confirm that the file ID is correct and accessible.Network or API Errors:
Temporary network issues or API downtime can cause failures. Retrying the operation or checking the API status may help.
Links and References
- Lexware Office API Documentation (official API docs for detailed resource and operation info)
- n8n Documentation (for general usage of the Lexware Office node)
If you need details on other operations or resources, feel free to ask!