Actions41
- Articles Actions
- Contacts Actions
- Dunnings Actions
- Invoices Actions
- Order Confirmations Actions
- Quotations Actions
- Voucher Lists Actions
- Vouchers Actions
- Countries Actions
- Files Actions
Overview
The node integrates with the Lexware API to perform various operations on different resources. Specifically, for the Invoices resource with the Get Many operation, it retrieves multiple invoices from the Lexware system. This is useful for scenarios where you need to fetch a list of invoices filtered by status and paginated by page number, such as generating reports, syncing invoice data with other systems, or monitoring outstanding payments.
Practical examples:
- Fetch all draft invoices on page 1 to review before sending.
- Retrieve all paid invoices to update accounting records.
- Get overdue invoices to trigger payment reminders.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of the invoice list to retrieve (pagination). |
| Status | Filter invoices by their status. Options: Draft, Sent, Paid, Overdue. |
Output
The node outputs an array of invoice objects in the json field. Each object represents an invoice retrieved from Lexware, containing details such as invoice ID, status, amounts, dates, and related metadata. The exact structure depends on the Lexware API response for invoices.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Lexware API via an API key credential configured in n8n.
- Network access to the Lexware service endpoint.
- Proper permissions on the Lexware account to read invoice data.
Troubleshooting
- Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Requesting a page number beyond available pages may return empty results.
- Filtering by an unsupported status value will likely result in no data or an error.
- Error messages:
- "Unsupported resource" if the resource parameter is incorrect.
- API errors related to rate limits or permission denied should be handled by checking credentials and API usage policies.
- Resolutions:
- Verify API credentials are correctly set up in n8n.
- Confirm the resource and operation parameters match supported values.
- Adjust pagination and filter parameters to valid ranges.
Links and References
- Lexware API Documentation (example placeholder, replace with actual URL)
- n8n documentation on creating and using API credentials
- General guide on pagination and filtering in APIs