Actions10
- Contacts Endpoint Actions
- Invoices Endpoint Actions
- Files Endpoint Actions
Overview
This node allows you to create a new person contact in LexOffice with both customer and vendor roles. It is designed for scenarios where an individual needs to be registered as both a customer and a vendor within your LexOffice account, enabling streamlined management of contacts who interact with your business in multiple capacities.
Common use cases:
- Registering freelancers or consultants who both purchase from and sell services/products to your company.
- Managing individuals who have dual relationships (e.g., a partner who is also a client).
- Automating onboarding processes for multi-role contacts in accounting workflows.
Practical example:
When a new consultant signs up via a web form, this node can automatically create their contact record in LexOffice as both a customer and a vendor, including their personal details, billing address, and contact information.
Properties
| Name | Type | Meaning |
|---|---|---|
| Person Details | Fixed Collection | Contains the individual's salutation, first name, and last name. |
| Salutation | String | The person's title (e.g., "Herr" or "Frau"). |
| First Name | String | The person's given name. |
| Last Name | String (Required) | The person's family name. |
| Billing Addresses | Fixed Collection | Specifies the billing address for the person. |
| Street | String | Street address for billing. |
| Zip | String | Postal code for billing address. |
| City | String | City for billing address. |
| Country Code | String | Country code in ISO 3166 alpha2 format (e.g., "DE" for Germany). |
| Additional Fields | Collection | Optional additional contact information. |
| Mobile Phone Number | String | The person's mobile phone number. |
| Private Phone Number | String | The person's private phone number. |
| Business Email | String | The person's business email address. |
Output
The node returns the response from LexOffice after creating the person contact. The output structure typically includes:
{
"id": "string", // Unique identifier for the created contact
"version": 0,
"roles": {
"customer": {},
"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"]
}
}
Note: The actual output may include additional fields returned by the LexOffice API.
Dependencies
- External Service: Requires access to the LexOffice API.
- API Key: You must configure valid LexOffice API credentials in n8n under the credential type
lexOfficeApi. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Missing Required Fields: If "Last Name" is not provided, the request will fail.
- Invalid Country Code: Ensure the country code is in ISO 3166 alpha2 format (e.g., "DE").
- Authentication Errors: Invalid or missing API credentials will result in authentication failures.
- API Rate Limits: Excessive requests may trigger rate limiting by LexOffice.
Error Messages and Resolutions:
"400 Bad Request": Check that all required fields are filled and formatted correctly."401 Unauthorized": Verify that your LexOffice API credentials are correct and active."422 Unprocessable Entity": Review the data types and formats, especially for nested fields like addresses and emails.