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 node integrates with the Lexware Office API to manage various business resources. Specifically, for the Dunning - Update operation, it updates an existing dunning record in the Lexware system. Dunning processes are typically used in accounting and finance to manage overdue invoices and send reminders to customers.
This node is beneficial when automating financial workflows such as updating dunning notices with new information or status changes. For example, a user might update the notes or tags on a dunning record after contacting a customer or adjusting payment terms.
Properties
| Name | Meaning |
|---|---|
| Dunning ID | The unique identifier of the dunning record to update (required). |
| Additional Fields | Optional fields to update on the dunning record: - Name: Name of the dunning. - Description: Description of the dunning. - Notes: Additional notes. - Tags: Tags associated with the dunning. - External ID: External system identifier for the dunning. |
Output
- The output is a JSON array containing the updated dunning resource object(s) returned from the Lexware Office API.
- Each item in the output corresponds to the updated dunning record with its current state after the update.
- The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the base URL configured in the credentials to make REST API calls.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If required fields for the update operation are missing, the node throws an error listing the missing fields. Ensure that the "Dunning ID" and any other mandatory fields are provided.
- Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify that the API key and resource URL are correctly set in the credentials.
- API Rate Limits: The Lexware API may enforce rate limits. If you encounter rate limit errors, consider reducing request frequency or increasing the configured API rate limit if supported.
- Invalid Field Values: Providing invalid values in additional fields (e.g., incorrect format for dates or IDs) may cause API errors. Validate input data before running the node.
Links and References
- Lexware Office API Documentation (official API docs for detailed resource and operation info)
- Dunning Process Overview (general explanation of dunning in accounting)
This summary focuses on the "Dunning" resource and the "Update" operation as requested, based on static analysis of the provided source code and property definitions.