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. Specifically, for the Voucher resource and the Get operation, it retrieves detailed information about a single voucher by its unique ID.
Typical use cases include:
- Fetching voucher details for accounting or financial workflows.
- Automating invoice or credit note retrieval in business processes.
- Integrating voucher data into other systems for reporting or auditing.
For example, you might use this node to get the details of a sales invoice voucher by providing its ID, then use that data downstream to update your CRM or ERP system.
Properties
| Name | Meaning |
|---|---|
| Voucher ID | The unique identifier of the voucher to retrieve. This is a required string input. |
Output
The node outputs an array of JSON objects representing the voucher data retrieved from the Lexware Office API. Each object contains all available fields of the voucher resource as returned by the API, such as voucher type, amounts, dates, status, and related 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 expects the base URL of the Lexware Office API to be configured in the credentials.
- No additional external dependencies are needed beyond the API access.
Troubleshooting
- Missing Required Fields Error: If the "Voucher ID" property is not provided, the node will throw an error indicating missing required fields. Ensure the Voucher ID is set.
- Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify the API key and resource URL in the credentials.
- Resource Not Found: If the voucher ID does not exist, the API may return a 404 or similar error. Confirm the voucher ID is correct.
- API Rate Limits: Excessive requests may hit rate limits; adjust usage or check API rate limit settings.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and voucher resource)
- n8n documentation on Using Credentials
- n8n community forums for integration tips and troubleshooting