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 perform various operations on different resources within the Lexware system. Specifically, for the Delivery Note resource with the Get operation, it retrieves detailed information about a specific delivery note by its ID.
Use cases include:
- Fetching delivery note details for order fulfillment or shipment tracking.
- Integrating delivery note data into other workflows such as invoicing, inventory management, or customer notifications.
- Automating retrieval of delivery documentation for reporting or auditing purposes.
Example: You have an order processing workflow where after creating a delivery note in Lexware, you want to fetch its details to send a confirmation email to the customer with the delivery information.
Properties
| Name | Meaning |
|---|---|
| Delivery Note ID | The unique identifier of the delivery note to retrieve. This is a required string input. |
Output
The node outputs a JSON array containing the delivery note data retrieved from the Lexware Office API. Each item in the output corresponds to one delivery note object with all its associated fields as returned by the API.
The exact structure depends on the Lexware API response but typically includes details such as delivery note number, date, items, quantities, customer info, status, and related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the Lexware Office API via an API key credential.
- The node expects the Lexware Office API base URL and API key to be configured in the credentials.
- Network access to the Lexware Office API endpoint is necessary.
Troubleshooting
- Missing Required Fields Error: If the "Delivery Note ID" is not provided, the node will throw an error indicating missing required fields.
- Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions to access delivery notes.
- Resource Not Found: If the specified delivery note ID does not exist, the API may return a 404 error; verify the ID correctness.
- API Rate Limits: Excessive requests might be throttled; check API rate limits and adjust usage accordingly.
- Network Issues: Connectivity problems to the Lexware API endpoint can cause failures; verify network and proxy settings.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and data structures)
- n8n Documentation on Creating Custom Nodes
- n8n Credentials Setup Guide for API Keys
If you need details on other operations or resources, feel free to ask!