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, allowing users to interact with various Lexware resources such as contacts, articles, invoices, vouchers, and more. Specifically, for the Article resource with the Get operation, the node retrieves detailed information about a single article by its unique ID.
Typical use cases include:
- Fetching detailed data about a specific product or service (article) stored in Lexware for further processing or reporting.
- Integrating Lexware article data into other workflows, such as inventory management, sales automation, or ERP systems.
- Automating retrieval of article details to update external systems or trigger notifications.
Example: A user wants to get the details of an article with ID "12345" to display its current price and description in a custom dashboard.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to retrieve. This is a required string input. |
Output
The node outputs a JSON array where each element corresponds to the retrieved article data object from Lexware Office API. The structure of the JSON object matches the article resource schema defined by Lexware, typically including fields like article name, description, type, pricing, tax rate, unit name, 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 uses the base URL provided in the credential configuration to send requests.
- No additional external dependencies are indicated beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If the "Article ID" property is not set or empty, the node will throw an error indicating missing required fields. Ensure that the Article ID is correctly provided.
- Authentication Errors: If the API key credential is invalid or missing, the node will fail to authenticate. Verify that the API key credential is correctly configured in n8n.
- Resource Not Found: If the specified Article ID does not exist in Lexware, the API may return a 404 error or empty response. Confirm that the Article ID is correct.
- API Rate Limits: Excessive requests might be throttled by the Lexware API. Adjust workflow frequency or check API rate limit settings if applicable.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n documentation on Using Credentials
- General information on Lexware Office
This summary focuses on the Article - Get operation based on the provided source code and property definitions.