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 interact with various resources, including Articles. Specifically, for the "Articles" resource and the "Get Many" operation, it retrieves multiple articles from the Lexware system. This is useful for workflows that need to fetch lists of product or service articles for further processing, reporting, or synchronization with other systems.
Practical examples include:
- Fetching a paginated list of product articles to update an e-commerce catalog.
- Retrieving service articles to generate reports or dashboards.
- Filtering articles by type (Product or Service) to process only relevant data subsets.
Properties
| Name | Meaning |
|---|---|
| Page | The page number of the article list to retrieve. Used for pagination. Default is 0 (first page). |
| Type | Filter articles by their type. Options are: Product, Service. |
Output
The node outputs an array of JSON objects representing the articles retrieved from Lexware. Each object corresponds to an article and contains its details as provided by the Lexware API.
If binary data were involved (e.g., files or attachments), it would be included in a separate binary property, but for this operation, the output is purely JSON data about articles.
Dependencies
- Requires an API key credential for authenticating with the Lexware API.
- The node depends on the Lexware API being accessible and properly configured.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication failures.
- Requesting a page number beyond available pages may return empty results.
- Using an unsupported article type filter could result in no data returned.
Error messages:
Unsupported resource: articles— indicates a misconfiguration or typo in the resource parameter.- Network or API errors typically indicate connectivity or permission problems; verify API keys and network access.
Resolutions:
- Ensure the API key credential is correctly set up in n8n.
- Verify the resource and operation parameters match supported values.
- Check Lexware API status and permissions if requests fail.
Links and References
- Lexware API Documentation (example placeholder link)
- n8n documentation on Creating Custom Nodes