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 manage various business resources, including dunnings (reminder notices for overdue payments). Specifically, the Dunning - Create operation allows users to create a new dunning record in their Lexware Office system.
Typical use cases include automating the creation of payment reminders for customers who have overdue invoices. For example, after an invoice becomes overdue, this node can be used to generate a dunning notice automatically, helping businesses streamline their accounts receivable processes and improve cash flow management.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to provide extra information about the dunning resource: |
| - Name | Name of the dunning resource |
| - Description | Description of the dunning resource |
| - Notes | Additional notes related to the dunning |
| - Tags | Tags associated with the dunning |
| - External ID | External identifier for the dunning resource |
These additional fields allow customization and enrichment of the dunning record during creation.
Output
The node outputs a JSON array where each element represents the response from the Lexware Office API for the created dunning resource. The structure of the JSON output corresponds to the API's representation of a dunning object, typically including identifiers, status, dates, and any metadata returned by the API.
If multiple items are processed, the output will contain multiple such objects.
The node does not explicitly handle binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the base URL of the Lexware Office API to be configured in the credentials.
- No other external dependencies are required.
Troubleshooting
Missing Required Fields Error:
If required fields for creating a dunning are missing, the node throws an error listing the missing fields. Ensure all mandatory parameters are provided before execution.Authentication Errors:
If the API key or resource URL is incorrect or missing, authentication will fail. Verify that the API key credential is correctly set up in n8n.API Rate Limits:
The Lexware Office API may enforce rate limits. If you encounter rate limit errors, consider reducing request frequency or increasing allowed limits if configurable.Network Issues:
Connectivity problems to the Lexware Office API endpoint will cause failures. Check network access and API availability.
Links and References
- Lexware Office API Documentation (official API docs for detailed resource and operation info)
- n8n Documentation (for general guidance on using API nodes and credentials)
This summary focuses on the "Dunning" resource with the "Create" operation as requested, based on static analysis of the provided source code and property definitions.