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, including invoices. Specifically, the Invoice Update operation allows users to update existing invoice records in Lexware Office. This is useful for scenarios where invoice details need to be modified after creation, such as correcting invoice information, adding notes, or updating tags.
Practical examples include:
- Updating the name or description of an invoice.
- Adding or modifying notes or tags associated with an invoice.
- Changing external identifiers linked to the invoice for integration purposes.
This operation helps maintain accurate and up-to-date invoice data within the Lexware Office system.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The unique identifier of the invoice to update (required). |
| Additional Fields | Optional fields to update on the invoice, including: |
| - Name: The name of the invoice. | |
| - Description: A description for the invoice. | |
| - Notes: Additional notes related to the invoice. | |
| - Tags: Comma-separated tags for categorization or filtering. | |
| - External ID: An external system identifier linked to the invoice. |
These properties allow flexible updates to various invoice attributes beyond just the core ID.
Output
The node outputs a JSON array where each element represents the updated invoice resource returned from the Lexware Office API after the update operation. The structure corresponds to the invoice object as defined by the Lexware Office API, typically including fields such as invoice ID, name, description, notes, tags, external IDs, and other invoice 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 uses the base URL provided in the credentials to send requests.
- No additional external dependencies are required beyond the configured API access.
Troubleshooting
- Missing Required Fields Error: If required fields like "Invoice ID" are not provided, the node throws an error listing missing fields. Ensure all mandatory inputs are set.
- Authentication Failures: Errors related to invalid or missing API keys will occur if credentials are not properly configured.
- API Rate Limits: The Lexware Office API may enforce rate limits; excessive requests might cause throttling errors.
- Invalid Field Values: Providing incorrect data types or unsupported values in additional fields can cause API errors. Validate input data before execution.
- To resolve issues, verify credentials, ensure required parameters are set, and check the Lexware Office API documentation for valid field formats.
Links and References
- Lexware Office API Documentation (official API docs for detailed resource and field definitions)
- n8n Documentation on Creating Custom Nodes (for general guidance on node development)
This summary focuses on the Invoice Update operation of the Lexware Office node based on static code analysis and provided property definitions.