LexOffice

LexOffice API Operations

Actions10

Contacts Endpoint Actions
Invoices Endpoint Actions
- Render an Invoice Document (PDF)
- Retrieve an Invoice
Files Endpoint Actions
- Download a File

Overview

The LexOffice node for n8n enables integration with the LexOffice API, specifically targeting contact management.
For the Contacts Endpoint resource and the Retrieve a Contact operation, this node allows users to fetch detailed information about a specific contact in their LexOffice account by providing the contact's unique ID.

Common scenarios:

Automating customer data retrieval for CRM or support workflows.
Enriching records in other systems (e.g., syncing contact details to another database).
Validating if a contact exists before performing further actions.

Practical example:
You could use this node to automatically pull up full contact details in response to a new ticket in your helpdesk system, ensuring agents have all relevant information at hand.

Properties

Name	Type	Meaning
Contact ID	String	The unique identifier of the contact to retrieve. Required. Returns the contact with the provided id value.

Output

The node returns the contact object as received from the LexOffice API.
The structure of the json output field will typically include:

{
  "id": "string",
  "version": number,
  "createdDate": "string",
  "updatedDate": "string",
  "roles": { /* ... */ },
  "company": { /* ... */ },
  "person": { /* ... */ },
  "addresses": { /* ... */ },
  "emailAddresses": { /* ... */ },
  "phoneNumbers": { /* ... */ },
  // ...other fields as defined by LexOffice API
}

All fields are directly passed through from the LexOffice API response.
No binary data is returned for this operation.

Dependencies

External Service: Requires access to the LexOffice API.
API Key: You must configure valid LexOffice API credentials in n8n under the name lexOfficeApi.
n8n Configuration: Ensure the LexOffice credential is set up and assigned to this node.

Troubleshooting

Common issues:

Invalid or missing Contact ID: If the provided Contact ID does not exist or is empty, the API will return an error.
Authentication errors: If the LexOffice API key is missing or invalid, you may receive a 401 Unauthorized error.
Network/API errors: Connectivity issues or LexOffice service downtime can cause failures.

Error messages and resolutions:

404 Not Found: The specified Contact ID does not exist. Double-check the ID.
401 Unauthorized: Check that your LexOffice API credentials are correctly configured in n8n.
400 Bad Request: The Contact ID format may be incorrect or missing. Ensure it is a valid string.