Lexware icon

Lexware

Interact with the Lexware API
Join our community

Actions41

Overview

This node integrates with the Lexware API to manage contact data, specifically allowing the creation of a new person contact. It is useful for automating the addition of individual contacts into the Lexware system, such as customers or vendors, directly from workflows. Practical examples include adding new client contacts after form submissions, syncing CRM contacts, or importing personnel data from other systems.

Properties

Name Meaning
Create as Customer? Boolean flag to set the role of the created person as a customer if enabled.
Create as Vendor? Boolean flag to set the role of the created person as a vendor if enabled.
Person Collection containing personal details: Salutation, First Name, Last Name of the person.
XRechnung Collection for electronic invoicing references: Buyer Reference and Vendor Number at Customer.
Email Addresses Fixed collection supporting multiple email addresses categorized as Business, Office, Private, Other. Each category can have multiple emails.
Phone Numbers Fixed collection supporting multiple phone numbers categorized as Business, Office, Mobile, Private, Fax, Other. Each category can have multiple numbers.
Note Text field for additional notes about the person.
Archived Boolean flag indicating if the contact should be archived.
Billing Address Fixed collection for billing address details including Supplement, Street, ZIP, City, Country Code (default "DE"). Supports multiple entries.
Shipping Address Fixed collection for shipping address details similar to billing address. Supports multiple entries.

Output

The node outputs JSON data representing the newly created person contact in Lexware. This includes all submitted fields and any additional metadata returned by the API. The output does not include binary data.

Dependencies

  • Requires an active connection to the Lexware API.
  • Needs an API authentication token configured in n8n credentials to authorize requests.
  • No other external dependencies are indicated.

Troubleshooting

  • Common issues:
    • Missing or invalid API credentials will cause authentication failures.
    • Providing incomplete mandatory person details (e.g., missing first or last name) may result in API validation errors.
    • Incorrect country codes or improperly formatted addresses might cause request rejections.
  • Error messages:
    • "Unsupported resource" error if the resource parameter is incorrect.
    • API errors related to roles if both "Create as Customer?" and "Create as Vendor?" flags conflict or are misused.
  • Resolutions:
    • Verify API credentials and permissions.
    • Ensure required person fields are filled correctly.
    • Validate address and contact formats before submission.

Links and References

Discussion