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, allowing users to perform various operations on different resources such as Articles, Contacts, Invoices, and more. Specifically, for the Contacts resource with the Delete operation, the node deletes a contact identified by a given Contact ID from the Lexware system.
This is useful in scenarios where you need to automate the removal of outdated or incorrect contact records from your Lexware database directly within an n8n workflow. For example, after processing customer data updates, you might want to clean up contacts that are no longer relevant.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to delete. This is a required string input. |
Output
The node outputs JSON data representing the result of the delete operation for each processed item. Typically, this will include confirmation of deletion or any relevant status information returned by the Lexware API.
If the node supports binary data output (not indicated here), it would typically represent files or attachments related to the resource, but for the Delete operation on Contacts, only JSON output is expected.
Dependencies
- Requires an active connection to the Lexware API.
- Needs an API authentication token or API key credential configured in n8n to authorize requests.
- No additional external dependencies are indicated.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: Ensure the Contact ID provided exists and is correctly formatted.
- Authentication errors: Verify that the API credentials are correctly set up and have sufficient permissions.
- Network or API downtime: Check connectivity and Lexware service status.
Error messages:
"Unsupported resource": Occurs if an invalid resource name is specified; ensure "contacts" is selected.- API error responses related to deletion failure usually indicate either the contact does not exist or insufficient permissions; verify the Contact ID and credentials.
Links and References
- Lexware API Documentation (Please replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes