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 Voucher resource with the Get All operation, it retrieves multiple voucher records from the Lexware system. Users can fetch all vouchers or limit the results with pagination and sorting options.
Typical use cases include:
- Retrieving a list of vouchers for reporting or auditing.
- Synchronizing voucher data between Lexware and other systems.
- Filtering vouchers by date, status, or other criteria to analyze financial documents.
For example, a user might want to get the latest 50 vouchers sorted by creation date descending or fetch all vouchers without limits for a full export.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all voucher results or only up to a given limit (boolean). |
| Limit | Maximum number of voucher results to return when not returning all (number, 1-250). |
| Page | Page number for pagination, zero-based index (number, minimum 0). |
| Sort | Sort order for the 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 (string). |
| Offset | Offset number for offset-based pagination (number, minimum 0). |
These properties allow flexible control over how many vouchers are retrieved and in what order, supporting both cursor and offset pagination styles.
Output
The node outputs an array of JSON objects representing vouchers retrieved from Lexware Office. Each object corresponds to a voucher record with fields as defined by the Lexware API's voucher schema.
If the "Return All" option is false, the output will contain up to the specified limit of voucher records; otherwise, it returns all available vouchers.
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 and API key from the configured credentials.
- No additional external dependencies beyond the Lexware Office API.
Troubleshooting
- Missing required fields error: If required parameters for the operation are missing, the node throws an error listing them. Ensure all mandatory inputs are provided.
- API authentication errors: Verify that the API key credential is correctly set up and has necessary permissions.
- Pagination issues: When using pagination, ensure that page, limit, cursor, and offset values are valid and consistent.
- Rate limiting: The Lexware API may enforce rate limits; if requests fail due to this, consider adjusting the request frequency or handling retries.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation on Credentials
- Pagination Concepts (general REST API pagination concepts)