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 Credit Note resource with the Get All operation, it retrieves a list of credit notes from the Lexware system. This is useful for scenarios where you need to fetch multiple credit notes for reporting, auditing, or further processing in workflows.
Typical use cases include:
- Retrieving all credit notes issued within a certain period.
- Fetching a limited number of credit notes with sorting and pagination.
- Integrating credit note data into other systems or dashboards.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all credit notes or limit the results. Options: true (all), false (limit) |
| Limit | Maximum number of credit notes to return when "Return All" is false. Range: 1 to 250 |
| Page | Page number for paginated results (0-based index) |
| Sort | Sort order for the results. Options include: - Created At (Ascending / Descending) - Updated At (Ascending / Descending) - Voucher Date (Ascending / Descending) - Name (Ascending / Descending) - ID (Ascending / Descending) |
| Cursor | Cursor string for cursor-based pagination |
| Offset | Offset number for offset-based pagination |
Output
The node outputs an array of JSON objects representing credit notes retrieved from Lexware Office. Each object contains the details of a credit note as provided by the Lexware API.
If the operation is set to "Get All" and "Return All" is false, the output will be limited to the specified number (Limit).
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for Lexware Office API authentication.
- The node uses the base URL configured in the credentials to connect to the Lexware Office API.
- No additional external dependencies are required beyond the API access.
Troubleshooting
- Missing Required Fields Error: If required parameters for the operation are missing, the node throws an error listing the missing fields. Ensure all mandatory inputs are provided.
- API Authentication Errors: If the API key or resource URL is incorrect or missing, authentication will fail. Verify the credentials configuration.
- Pagination Issues: When using pagination properties (
Page,Cursor,Offset), ensure values are within valid ranges to avoid empty or unexpected results. - Rate Limits: The Lexware 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 node usage and credential setup)