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 retrieve dunning records. Specifically, the "Dunning - Get All" operation fetches multiple dunning entries from the system, supporting pagination, sorting, and filtering options. This is useful for automating workflows that require monitoring or processing outstanding payment reminders (dunnings) in accounting or financial management systems.
Practical examples include:
- Automatically retrieving all open dunning notices to trigger follow-up emails.
- Fetching a limited set of recent dunnings sorted by creation date for reporting.
- Paginating through large sets of dunning data to sync with external databases.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all dunning results or limit the number of results |
| Limit | Maximum number of dunning records to return (used if Return All is false) |
| Page | Page number for paginated results (0-based index) |
| Sort | Sort order for the results. Options: Created At (Asc/Desc), Updated At (Asc/Desc), Voucher Date (Asc/Desc), Name (Asc/Desc), ID (Asc/Desc) |
| Cursor | Cursor string for cursor-based pagination |
| Offset | Offset number for offset-based pagination |
Output
The node outputs an array of JSON objects representing dunning records retrieved from Lexware Office. Each object contains the fields as defined by the Lexware API for dunnings, such as IDs, status, dates, amounts, and related metadata.
If binary data output is supported (not indicated here for this operation), it would typically represent downloadable files like PDFs of dunning documents.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the base URL provided by the credential configuration to make HTTP requests.
- No additional external dependencies are required beyond the configured API access.
Troubleshooting
- Missing Required Fields Error: If required parameters for the operation are not provided, the node throws an error listing missing fields. Ensure all mandatory inputs are set.
- API Authentication Failures: Errors related to invalid or missing API keys will occur if credentials are misconfigured.
- Pagination Issues: When using pagination properties (Page, Cursor, Offset), ensure values are within valid ranges to avoid empty or repeated results.
- Rate Limits: The Lexware API may enforce rate limits; excessive requests might cause temporary failures.
To resolve errors:
- Verify API credentials and permissions.
- Check input property values for correctness.
- Consult Lexware API documentation for specific error codes and messages.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)