Actions41
- Articles Actions
- Contacts Actions
- Dunnings Actions
- Invoices Actions
- Order Confirmations Actions
- Quotations Actions
- Voucher Lists Actions
- Vouchers Actions
- Countries Actions
- Files Actions
Overview
This node integrates with the Lexware API to perform various operations on different resources, including Articles. Specifically, for the "Articles" resource and the "Delete" operation, the node deletes an article identified by its unique Article ID. This is useful in scenarios where you need to programmatically remove outdated or incorrect articles from your Lexware system as part of automated workflows.
Practical examples include:
- Automatically deleting product articles that are discontinued.
- Cleaning up test or temporary articles created during data import processes.
- Managing inventory by removing obsolete articles based on business rules.
Properties
| Name | Meaning |
|---|---|
| Article ID | The unique identifier of the article to delete |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this will include confirmation of deletion or details about the deleted article. The exact structure depends on the Lexware API response but generally confirms success or failure of the deletion request.
No binary data output is expected for this operation.
Dependencies
- Requires a valid API key credential for authenticating with the Lexware API.
- The node must be configured with appropriate credentials in n8n to access the Lexware service.
- Network connectivity to the Lexware API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing Article ID: Ensure the Article ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Network or API downtime: Check network connectivity and Lexware service status.
Error messages:
"Unsupported resource: articles": Occurs if the resource parameter is incorrectly set; ensure it is exactly "articles".- API error responses indicating article not found or permission denied should be handled by verifying input and credentials.
Links and References
- Lexware API Documentation (example placeholder link)
- n8n documentation on creating custom nodes