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 such as contacts, articles, invoices, credit notes, and more. Specifically, for the Credit Note resource with the Update operation, it allows users to update existing credit note records in their Lexware Office system.
Typical use cases include automating updates to credit notes based on external triggers or workflows, such as correcting details, adding notes, or tagging credit notes after certain events occur in other systems.
For example, a user might update the description or add tags to a credit note after a customer service interaction, or synchronize credit note data from another accounting system.
Properties
| Name | Meaning |
|---|---|
| Credit Note ID | The unique identifier of the credit note to update (required). |
| Additional Fields | Optional fields to update on the credit note, including: |
| - Name: Name of the credit note. | |
| - Description: Description text for the credit note. | |
| - Notes: Additional notes related to the credit note. | |
| - Tags: Comma-separated tags for categorization. | |
| - External ID: An external system identifier for the credit note. |
These properties allow specifying which credit note to update and what fields to modify.
Output
The node outputs an array of JSON objects representing the updated credit note(s) returned by the Lexware Office API. Each object contains the full details of the credit note after the update, reflecting all current fields including those modified.
No binary data output is involved in 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.
- 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 "Credit Note ID" is provided and any mandatory fields required by the API are included.
- Authentication Errors: If the API key or base URL is incorrect or missing, authentication will fail. Verify the credential configuration.
- API Rate Limits: The Lexware Office API may enforce rate limits; if exceeded, requests may be rejected. Adjust workflow frequency or handle retries accordingly.
- Invalid Field Values: Providing invalid values in additional fields (e.g., malformed tags or unsupported characters) may cause API errors. Validate input data before sending.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n Documentation (for general node usage and credential setup)
This summary focuses on the "Credit Note" resource with the "Update" operation as requested, describing its inputs, outputs, and behavior based on static analysis of the provided source code and property definitions.