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 Article resource and the Update operation, it allows users to update existing articles in their Lexware system by specifying the article ID and any fields they want to modify.
Typical use cases include:
- Updating product or service details such as name, description, tags, or external IDs.
- Keeping inventory or catalog information current by modifying article attributes.
- Automating updates to articles based on external data sources or workflows.
For example, a user might update an article's description and tags after receiving new marketing information or correct a typo in the article name.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to update (required). |
| Additional Fields | Optional fields to update on the article: |
| - Name: New name of the article. | |
| - Description: Updated description text. | |
| - Notes: Additional notes related to the article. | |
| - Tags: Comma-separated tags for categorization. | |
| - External ID: Identifier used in external systems for this article. |
Output
The node outputs a JSON array where each element corresponds to the updated article object returned from the Lexware Office API. This typically includes all article properties after the update, reflecting the changes made.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the base URL provided by the credential configuration to send requests.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If required fields like "Article ID" are not provided, the node will throw an error listing missing fields. Ensure all mandatory inputs are set.
- Authentication Failures: Errors related to invalid or missing API keys indicate issues with credential setup. Verify that the API key credential is correctly configured.
- API Request Errors: Network issues or invalid field values may cause API errors. Check the input values and network connectivity.
- Partial Updates Not Reflected: Ensure that the fields you want to update are included in the "Additional Fields" collection; otherwise, they won't be changed.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n documentation on creating custom nodes for further customization guidance