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 Contact resource and the Update operation, it allows users to update existing contact records in their Lexware Office system. This is useful for keeping contact information current, such as updating names, descriptions, notes, tags, or external IDs associated with a contact.
Typical use cases include:
- Synchronizing contact details from other systems into Lexware Office.
- Automating updates to customer or vendor information based on external triggers.
- Maintaining accurate contact metadata for reporting or communication purposes.
For example, you might update a contact's name and add new tags after receiving updated customer data from a CRM system.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to update (required). |
| Additional Fields | Optional fields to update on the contact: |
| - Name: Name of the contact. | |
| - Description: Description of the contact. | |
| - Notes: Additional notes related to the contact. | |
| - Tags: Comma-separated tags for categorization. | |
| - External ID: An external system identifier for the contact. |
Output
The node outputs an array of JSON objects representing the updated contact(s) returned by the Lexware Office API. Each object contains the contact's data after the update operation, reflecting any changes made.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the Lexware Office API base URL and API key to be configured in the credentials.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If required fields for the update operation are missing, the node throws an error listing the missing fields. Ensure that the "Contact ID" and any mandatory fields are provided.
- Authentication Errors: If the API key or base URL credentials are incorrect or missing, authentication will fail. Verify credentials configuration.
- API Rate Limits: The Lexware Office API may enforce rate limits; excessive requests might be throttled. Adjust usage accordingly.
- Invalid Contact ID: Providing a non-existent or malformed Contact ID will result in an error from the API. Confirm the Contact ID is valid.
- Continue On Fail: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation (for general node usage and credential setup)
Note: This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.