Actions5
Overview
This node allows n8n workflows to interact with the Lexoffice Public API, specifically to retrieve information about a contact using the "API Contact GET" operation. It is useful in scenarios where you need to fetch detailed data for a specific contact stored in your Lexoffice account, such as synchronizing contact details with other systems, enriching CRM records, or automating business processes that depend on up-to-date contact information.
Practical Example:
You could use this node to automatically pull contact details from Lexoffice when a new order is received, ensuring your sales or support team always has the latest customer information.
Properties
| Name | Type | Meaning |
|---|---|---|
| Category | options | The type of resource to interact with. For this operation, should be set to "Contacts". |
| Contact ID | string | The unique identifier of the contact to retrieve from Lexoffice. Required for this call. |
Output
- json: The output will contain the full JSON response returned by the Lexoffice API for the specified contact. This typically includes all available fields for the contact, such as name, address, email, phone numbers, and any other metadata provided by Lexoffice.
Dependencies
- External Service: Requires access to the Lexoffice Public API.
- Credentials: You must configure the
lexofficePuplicApicredential in n8n, which should include:domain: The base URL for the Lexoffice API.token: A valid API token for authentication.
Troubleshooting
Common Issues:
- Invalid Credentials: If the API token or domain is incorrect, the node will throw an authentication error. Double-check your credentials in n8n.
- Missing Contact ID: The "Contact ID" property is required. If omitted or invalid, the API will return an error indicating the contact was not found.
- No API Item Found: If the combination of category and operation does not match any supported API endpoint, the node will throw a "No API Item found" error. Ensure "Category" is set to "Contacts" and "Operation" to "API Contact GET".
- JSON Parsing Errors: If the node expects a JSON body and receives malformed input, it may return a parsing error.
Error Messages:
"No API Item found": Indicates an unsupported or misconfigured category/operation. Check your property selections.- API errors (e.g., 404, 401): These are passed through from Lexoffice and usually indicate missing resources or authentication issues.