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 invoices. Specifically, the "Invoice" resource with the "Get" operation allows users to retrieve detailed information about a specific invoice by its ID. This is useful in scenarios where you need to fetch invoice data for processing, reporting, or integration with other systems.
Practical examples include:
- Automatically retrieving invoice details after creation for further automation.
- Fetching invoice data to update records in an external CRM or accounting system.
- Using invoice information to trigger notifications or workflows based on invoice status.
Properties
| Name | Meaning |
|---|---|
| Invoice ID | The unique identifier of the invoice to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the invoice details retrieved from the Lexware Office API. The structure includes all relevant invoice fields as provided by the API, such as invoice number, date, contact information, amounts, status, and other 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 Lexware Office API base URL and API key to be configured in the credentials.
- No additional external dependencies are specified.
Troubleshooting
- Missing Required Fields Error: If the "Invoice ID" is not provided, the node will throw an error indicating missing required fields. Ensure that the Invoice ID is correctly set.
- 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.
- Resource Not Found: If the specified Invoice ID does not exist, the API may return an error or empty result. Confirm the Invoice ID is correct.
- API Rate Limits: Excessive requests may hit rate limits imposed by the Lexware API. Adjust usage or check API rate limit settings if errors occur.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n documentation on Using Credentials for setting up API keys
This summary focuses on the "Invoice" resource with the "Get" operation as requested, based on static analysis of the provided source code and property definitions.