Lexware icon

Lexware

Interact with the Lexware API
Join our community

Actions41

Overview

The node integrates with the Lexware API to manage contact data, specifically allowing updates to existing contacts. It is useful in scenarios where you need to programmatically modify contact details such as company information, tax identifiers, roles (customer/vendor), addresses, and communication details within an automated workflow. For example, you might update a customer's billing address or add new contact persons after receiving updated information from a CRM system.

Properties

Name Meaning
Contact ID The unique identifier of the contact to update. This is required to specify which contact record will be modified.
Company Name The name of the company associated with the contact.
Tax Number The tax number assigned to the company/contact.
VAT Registration ID The VAT registration identification number for tax purposes.
Create as Customer? Boolean flag indicating whether to assign the "customer" role to this contact.
Create as Vendor? Boolean flag indicating whether to assign the "vendor" role to this contact.
Allow Tax Free Invoices Boolean flag to allow issuing tax-free invoices to this contact.
Contact Persons A collection of one or more contact persons related to the company, each with salutation, first name, last name, primary status, email, and phone number.
XRechnung Collection containing electronic invoice-related fields: Buyer Reference and Vendor Number at Customer.
Email Addresses Multiple categorized email addresses (Business, Office, Private, Other), each supporting multiple entries.
Phone Numbers Multiple categorized phone numbers (Business, Office, Mobile, Private, Fax, Other), each supporting multiple entries.
Note A textual note about the contact.
Archived Boolean flag indicating if the contact is archived (inactive).
Billing Address One or more billing addresses, each including supplement, street, ZIP code, city, and country code (default "DE").
Shipping Address One or more shipping addresses, structured similarly to billing addresses.

Output

The node outputs an array of JSON objects representing the updated contact(s) as returned by the Lexware API. Each object contains the full contact data reflecting the changes made, including updated fields and any additional metadata provided by the API.

If binary data were involved (not indicated here), it would typically represent files or attachments related to the contact, but this operation focuses on JSON data only.

Dependencies

  • Requires an active connection to the Lexware API.
  • Needs an API authentication token or API key credential configured in n8n to authorize requests.
  • The node depends on internal action modules that handle the actual API calls for contacts operations.

Troubleshooting

  • Common Issues:

    • Invalid or missing Contact ID will cause the update to fail because the API cannot identify which contact to modify.
    • Providing improperly formatted addresses or emails may result in validation errors from the API.
    • Network or authentication failures can prevent successful API communication.

  • Error Messages:

    • "Unsupported resource: contacts" — indicates the resource parameter was not set correctly; ensure "Contacts" is selected.
    • API errors related to authorization usually mean the API key or token is invalid or expired; reconfigure credentials.
    • Validation errors from the API often include messages about required fields or incorrect formats; verify input data accordingly.

Links and References

Discussion