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, allowing users to interact with various Lexware resources programmatically. Specifically, for the Dunning resource with the Get operation, it retrieves detailed information about a specific dunning record by its ID.
Use cases include automating the retrieval of dunning notices (reminders for overdue payments) within business workflows, such as fetching dunning details to trigger follow-up actions or reporting.
Example: Automatically fetch a dunning notice by its ID after a payment is overdue, then send a customized reminder email based on the retrieved data.
Properties
| Name | Meaning |
|---|---|
| Dunning ID | The unique identifier of the dunning record to retrieve (required). |
Output
The node outputs a JSON array where each item corresponds to the retrieved dunning resource data from Lexware Office. The structure reflects the dunning object's properties as returned by the Lexware API, typically including fields like status, customer info, amounts due, dates, and related metadata.
No binary data output is indicated for this operation.
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.
- Network connectivity to the Lexware Office API endpoint is necessary.
Troubleshooting
- Missing Required Fields Error: If the "Dunning ID" is not provided or empty, the node will throw an error indicating missing required fields. Ensure the Dunning ID is correctly set.
- Authentication Errors: If the API key credential is invalid or missing, authentication errors will occur. Verify that the API key credential is properly configured.
- Resource Not Found: If the specified Dunning ID does not exist, the API may return a 404 or similar error. Confirm the ID is correct.
- API Rate Limits: Excessive requests might be throttled; check API rate limits and adjust usage accordingly.
- Network Issues: Connectivity problems can cause request failures; ensure stable internet access.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation - Creating Custom Nodes
- Handling API Credentials in n8n
This summary is based solely on static analysis of the provided source code and property definitions.