Actions61
- Contact Actions
- Article Actions
- Voucher Actions
- Invoice Actions
- Down Payment Invoice Actions
- Quotation Actions
- Credit Note Actions
- Delivery Note Actions
- Dunning Actions
- File Actions
- Profile Actions
- Country Actions
- Payment Condition Actions
- Event Subscription Actions
- Recurring Template Actions
- Voucherlist Actions
- Trigger Actions
Overview
This node integrates with the Lexware Office API to manage various business resources such as contacts, articles, invoices, vouchers, and more. Specifically, for the Contact - Get operation, it retrieves detailed information about a single contact by its unique ID.
Typical use cases include:
- Fetching contact details to enrich customer data in workflows.
- Retrieving contact information before creating or updating related records like invoices or orders.
- Automating CRM updates or synchronizations with Lexware Office.
Example: You have a workflow that processes incoming orders and needs to fetch the customer's contact details from Lexware Office by their Contact ID to personalize communications or validate data.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. This is a required string input field. |
Output
The node outputs an array of JSON objects representing the contact data retrieved from Lexware Office. Each object contains all available fields of the contact resource as returned by the API, such as name, email, phone, address, VAT number, tax number, and role.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the Lexware Office API base URL and API key to be configured in the credentials.
- Network access to the Lexware Office API endpoint is necessary.
Troubleshooting
- Missing Contact ID: If the Contact ID property is not provided or empty, the node will throw an error indicating missing required fields.
- Authentication Errors: Invalid or missing API key credentials will cause authentication failures. Ensure the API key is correctly set up in the node credentials.
- Resource Not Found: If the specified Contact ID does not exist, the API may return a 404 error or empty result. Verify the Contact ID is correct.
- API Rate Limits: Exceeding the allowed request rate may result in throttling errors. Adjust the workflow frequency or check API rate limit settings.
- Network Issues: Connectivity problems to the Lexware Office API endpoint will cause request failures. Check network and firewall settings.
Links and References
- Lexware Office API Documentation (official API docs)
- n8n Documentation on Credentials (for setting up API keys)
This summary focuses on the "Contact" resource with the "Get" operation as requested, based on static analysis of the provided source code and input properties.