Actions41
- Articles Actions
- Contacts Actions
- Dunnings Actions
- Invoices Actions
- Order Confirmations Actions
- Quotations Actions
- Voucher Lists Actions
- Vouchers Actions
- Countries Actions
- Files Actions
Overview
The node integrates with the Lexware API to perform various operations on different resources, including Contacts. Specifically, for the Contacts resource with the "Get" operation, it retrieves detailed information about a single contact identified by a unique Contact ID. This is useful in scenarios where you need to fetch up-to-date contact details from your Lexware system within an automated workflow, such as syncing contact data to a CRM, verifying contact information before processing orders, or generating reports.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. This is a required string input. |
Output
The node outputs JSON data representing the retrieved contact's details. The structure typically includes fields such as contact name, address, phone number, email, and other relevant contact attributes as provided by the Lexware API. The output is designed to be consumed by subsequent nodes in the workflow for further processing or integration.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Lexware API via an API key credential configured in n8n.
- The node depends on network access to the Lexware service endpoint.
- Proper permissions on the API key are necessary to read contact information.
Troubleshooting
- Common Issues:
- Invalid or missing Contact ID will result in errors or empty responses.
- Network connectivity problems can cause request failures.
- Insufficient API permissions may lead to authorization errors.
- Error Messages:
"Unsupported resource: contacts"— indicates a misconfiguration of the resource parameter.- API errors returned from Lexware (e.g., "Contact not found") should be checked against the Contact ID used.
- Resolutions:
- Verify that the Contact ID is correct and exists in Lexware.
- Ensure the API key credential is valid and has appropriate permissions.
- Check network connectivity and Lexware service status.
Links and References
- Lexware API Documentation (example placeholder, replace with actual URL if available)
- n8n Documentation on Creating Custom Nodes