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 such as articles, contacts, dunnings, invoices, and more. Specifically, for the "Dunnings" resource with the "Get" operation, the node retrieves detailed information about a specific dunning (a reminder or collection notice related to unpaid invoices) by its unique identifier. This is useful in scenarios where businesses need to automate fetching dunning details for follow-up actions, reporting, or integration with other systems.
Practical examples include:
- Automatically retrieving dunning details to send reminders to customers.
- Integrating dunning data into CRM or accounting workflows.
- Generating reports on outstanding payments and their associated dunnings.
Properties
| Name | Meaning |
|---|---|
| Dunning ID | The unique identifier of the dunning record to retrieve. This is required to specify which dunning's details to fetch. |
Output
The node outputs JSON data representing the details of the requested dunning. This typically includes fields such as the dunning ID, customer information, amounts due, dates, status, and any other metadata provided by the Lexware API for that dunning record.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the dunning, but this is not evident from the provided code.
Dependencies
- Requires an active connection to the Lexware API.
- Needs an API authentication token or key configured in the node credentials to authorize requests.
- The node depends on the Lexware API being accessible and responsive.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Dunning ID will likely result in an error or empty response.
- Network connectivity problems can cause request failures.
- Missing or incorrect API credentials will prevent successful authentication.
Error messages:
- Errors indicating unsupported resources suggest misconfiguration of the resource parameter.
- Authentication errors imply issues with the API key or token setup.
- Not found errors usually mean the specified Dunning ID does not exist.
Resolutions:
- Verify the Dunning ID is correct and exists in Lexware.
- Ensure API credentials are properly set up and valid.
- Check network connectivity and Lexware API status.
Links and References
- Lexware API Documentation (example placeholder link)
- n8n documentation on creating custom nodes