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. Specifically, for the Delivery Note resource with the Get All operation, it retrieves a list of delivery notes from the Lexware system. This is useful for scenarios where you need to fetch multiple delivery note records for reporting, synchronization, or further processing in workflows.
For example, you might use this node to:
- Retrieve all delivery notes created within a certain date range.
- Fetch a paginated list of delivery notes sorted by creation date.
- Integrate delivery note data into an ERP or CRM system.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit (true/false). |
| Limit | Maximum number of results to return when not returning all (1 to 250). |
| Page | Page number for pagination (0-based index). |
| Sort | Sort order for results. Options: |
| - Created At (Ascending) | |
| - Created At (Descending) | |
| - Updated At (Ascending) | |
| - Updated At (Descending) | |
| - Voucher Date (Ascending) | |
| - Voucher Date (Descending) | |
| - Name (Ascending) | |
| - Name (Descending) | |
| - ID (Ascending) | |
| - ID (Descending) | |
| Cursor | Cursor string for cursor-based pagination (optional). |
| Offset | Offset number for offset-based pagination (minimum 0). |
These properties allow fine control over how many delivery notes are fetched and how they are ordered and paginated.
Output
The node outputs an array of JSON objects representing delivery notes. Each object corresponds to a delivery note record retrieved from the Lexware Office API.
The exact structure of each delivery note object depends on the API response but typically includes fields such as:
- Delivery note ID
- Creation and update timestamps
- Voucher date
- Customer and item details
- Status and other metadata
No binary data output is indicated for this operation.
Dependencies
- Requires connection to the Lexware Office API.
- An API key credential must be configured in n8n to authenticate requests.
- The node uses the base URL and API key from the configured credentials to make API calls.
Troubleshooting
- Missing required fields error: If required parameters are missing for the operation, the node will throw an error listing the missing fields. Ensure all mandatory inputs are provided.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Pagination issues: When using pagination properties (
limit,page,cursor,offset), ensure values are within allowed ranges to avoid empty or incomplete results. - Rate limiting: The API may enforce rate limits; if exceeded, requests may fail temporarily. Adjust workflow frequency or handle retries accordingly.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation (for general usage of nodes and credentials)
If you need details about other operations or resources, feel free to ask!