LexOffice icon

LexOffice

LexOffice API Operations

Actions10

Overview

The Create Person - Vendor operation in the LexOffice n8n node allows you to create a new person contact with the "vendor" role in your LexOffice account. This is useful for businesses that need to manage suppliers or service providers as contacts within their accounting and invoicing workflows.

Common scenarios:

  • Onboarding a new supplier into your LexOffice system.
  • Automating vendor creation when receiving data from another system (e.g., CRM, procurement).
  • Integrating supplier registration forms with LexOffice via n8n.

Practical example:
When a new vendor signs up through your website, this node can automatically add their details to LexOffice, including their name, address, and contact information.

Properties

Name Type Meaning
Person Details Fixed Collection Contains personal information about the vendor, such as salutation, first name, and last name.
  Salutation String The salutation for the person (e.g., "Herr" or "Frau").
  First Name String The first name of the person.
  Last Name String (Required) The last name of the person.
Billing Addresses Fixed Collection Specifies the billing address for the vendor.
  Street String The street part of the billing address.
  Zip String The postal code for the billing address.
  City String The city for the billing address.
  Country Code String Country code in ISO 3166 alpha2 format (e.g., "DE" for Germany).
Additional Fields Collection Optional additional contact information for the vendor.
  Mobile Phone Number String Mobile phone number of the person.
  Private Phone Number String Private phone number of the person.
  Business Email String Business email address of the person.

Output

The node returns the response from the LexOffice API after creating the vendor contact. The output structure typically includes:

{
  "id": "string",              // Unique identifier for the created contact
  "version": 0,
  "roles": {
    "vendor": {}
  },
  "person": {
    "salutation": "string",
    "firstName": "string",
    "lastName": "string"
  },
  "addresses": {
    "billing": [
      {
        "street": "string",
        "zip": "string",
        "city": "string",
        "countryCode": "string"
      }
    ]
  },
  "emailAddresses": {
    "business": ["string"]
  },
  "phoneNumbers": {
    "mobile": ["string"],
    "private": ["string"]
  }
}
  • The actual fields returned may vary depending on the LexOffice API response.
  • No binary data is produced by this operation.

Dependencies

  • LexOffice API: Requires a valid LexOffice API key configured in n8n credentials under lexOfficeApi.
  • n8n Configuration: Ensure the LexOffice node is properly installed and credentials are set up.

Troubleshooting

Common issues:

  • Missing Required Fields: If "Last Name" is not provided, the API will likely return an error.
  • Invalid Country Code: The country code must be in ISO 3166 alpha2 format (e.g., "DE").
  • Authentication Errors: Invalid or missing API key will result in authentication failures.

Error messages and resolutions:

  • "401 Unauthorized": Check your LexOffice API credentials in n8n.
  • "400 Bad Request": Review input fields for missing required values or incorrect formats.
  • "422 Unprocessable Entity": Ensure all fields meet LexOffice's validation requirements (e.g., valid email format).

Links and References

Discussion