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, including delivery notes. Specifically, the Delivery Note - Update operation allows users to update an existing delivery note by specifying its ID and providing additional fields to modify.
Typical use cases include:
- Updating details of a delivery note after creation, such as changing its name, description, notes, tags, or external ID.
- Automating updates to delivery notes in workflows where delivery information changes or corrections are needed.
- Synchronizing delivery note data between Lexware Office and other systems.
Example: A user can update the notes and tags of a delivery note identified by its ID to add new remarks or categorize it differently.
Properties
| Name | Meaning |
|---|---|
| Delivery Note ID | The unique identifier of the delivery note to update (required). |
| Additional Fields | Optional collection of fields to update on the delivery note, including: |
| - Name: Name of the delivery note. | |
| - Description: Description text for the delivery note. | |
| - Notes: Additional notes related to the delivery note. | |
| - Tags: Comma-separated tags for categorization. | |
| - External ID: An external system identifier for the delivery note. |
Output
The node outputs a JSON array containing the updated delivery note object(s) returned from the Lexware Office API. Each item in the output corresponds to one updated resource and includes all relevant fields as provided by the API response.
No binary data output is produced by 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 send requests.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If required fields like "Delivery Note ID" are not provided, the node will throw an error indicating missing required fields. Ensure that the delivery note ID is specified.
- Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify that the API key is correctly configured in the node credentials.
- API Request Failures: Network issues or incorrect resource IDs may cause request failures. Check the delivery note ID validity and network connectivity.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if some fail, returning error messages in the output array.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n documentation on creating custom nodes
This summary focuses on the "Delivery Note" resource and the "Update" operation as requested, based on static analysis of the provided source code and property definitions.