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
This node integrates with the Lexware Office API to perform various operations on different resources, including dunnings. Specifically, for the Dunning - Document operation, it renders a dunning document as a PDF. This is useful in scenarios where you need to generate official dunning letters (reminder notices for overdue payments) programmatically within an automation workflow.
Practical examples include:
- Automatically generating and sending dunning documents to customers when invoices become overdue.
- Archiving or storing dunning PDFs in a document management system.
- Integrating dunning document generation into broader financial or CRM workflows.
Properties
| Name | Meaning |
|---|---|
| Dunning ID | The unique identifier of the dunning record for which the document will be rendered as a PDF. This property is required. |
Output
The node outputs JSON data representing the result of the dunning document rendering operation. Typically, this will include metadata about the generated PDF document or a direct link/reference to the PDF file.
If the node supports downloading files (e.g., the "Download File" operation), it may also output binary data representing the actual PDF content. However, for the "Document" operation specifically, the output is JSON describing the rendered document.
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 other external dependencies are indicated.
Troubleshooting
- Missing Required Fields Error: If the required "Dunning ID" is not provided, the node will throw an error indicating missing required fields. Ensure that the Dunning ID is correctly set.
- Authentication Errors: If the API key credential is invalid or missing, the node will fail to authenticate with the Lexware Office API. Verify that the API key is correct and properly configured.
- API Endpoint Issues: Network issues or incorrect resource URLs can cause failures. Confirm that the base URL in the credentials is accurate and reachable.
- Unexpected Response Format: If the API changes or returns unexpected data, the node might not handle it correctly. Check API documentation and update the node or credentials accordingly.
Links and References
- Lexware Office API Documentation (official API docs for detailed information on dunning and document operations)
- n8n Documentation (for general guidance on using custom nodes and credentials)
This summary focuses on the "Dunning" resource and the "Document" operation as requested, based on static analysis of the provided source code and input properties.