Actions10
- Contacts Endpoint Actions
- Invoices Endpoint Actions
- Files Endpoint Actions
Overview
The Create Person - Customer operation in the LexOffice n8n node allows you to create a new person contact with a customer role in your LexOffice account. This is useful for automating the onboarding of new customers, syncing CRM data, or integrating LexOffice with other business tools. For example, you could automatically add a new customer to LexOffice when a lead is converted in your sales system.
Properties
| Name | Type | Meaning |
|---|---|---|
| Person Details | Fixed Collection | Information about the person being created, including salutation, first name, and last name. |
| Salutation | String | The person's salutation (e.g., "Herr" or "Frau"). |
| First Name | String | The person's first name. |
| Last Name | String (Required) | The person's last name. |
| Billing Addresses | Fixed Collection | Billing address details for the person. |
| Street | String | Street address for billing. |
| Zip | String | ZIP/postal code for billing. |
| City | String | City for billing. |
| 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 | 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 output will be a JSON object representing the newly created person contact in LexOffice. The structure typically includes:
{
"id": "string",
"version": 0,
"roles": {
"customer": {}
},
"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 which properties you provide.
- No binary data is returned by this operation.
Dependencies
- LexOffice API: Requires a valid LexOffice API key configured as an n8n credential named
lexOfficeApi. - n8n Configuration: Ensure that the LexOffice node is properly installed and credentials are set up in your n8n instance.
Troubleshooting
- Missing Required Fields: If "Last Name" is not provided in "Person Details", the request will fail. Always ensure required fields are filled.
- Invalid Country Code: The country code must be in ISO 3166 alpha2 format (e.g., "DE"). Using an incorrect format will result in an error from the API.
- Authentication Errors: If the API key is missing or invalid, you will receive authentication errors. Double-check your credentials in n8n.
- API Rate Limits: Excessive requests may trigger rate limiting by LexOffice. Monitor your usage if you encounter 429 errors.