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 Contact resource with the Get All operation, it retrieves a list of contacts from the Lexware system. This is useful for scenarios where you need to fetch multiple contact records for processing, reporting, or synchronization with other systems.
Typical use cases include:
- Exporting all customer or vendor contacts for CRM updates.
- Fetching a paginated list of contacts for display or further automation.
- Sorting contacts by creation date, name, or other criteria to prioritize processing.
Properties
| Name | Meaning |
|---|---|
| Return All | Whether to return all results or only up to a given limit (boolean). |
| Limit | Maximum number of 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 results. Options: - 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 (string). |
| Offset | Offset number for offset-based pagination (number, minimum 0). |
Output
The node outputs an array of JSON objects representing contacts retrieved from Lexware Office. Each object corresponds to a contact record with fields as defined by the Lexware API's contact schema (e.g., contact ID, name, email, phone, address, etc.).
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 to make requests.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If required parameters for certain operations are missing, the node throws an error listing the missing fields. For "Get All" on Contact, this is unlikely but possible if internal validation fails.
- API Authentication Errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Pagination Issues: When using pagination properties (
Page,Limit,Cursor,Offset), ensure values are within allowed ranges to avoid empty or partial results. - Rate Limits: The Lexware API may enforce rate limits; if exceeded, requests might fail temporarily. Adjust usage or implement retries accordingly.
Links and References
- Lexware Office API Documentation (official API docs for detailed resource schemas and endpoints)
- n8n documentation on Using Credentials
- General info on Pagination Patterns