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
The Lexware Office node integrates with the Lexware Office API, enabling users to interact programmatically with various business resources such as contacts, invoices, articles, and more. Specifically, the Trigger resource with the Trigger operation allows users to set up webhook event triggers for specific Lexware events (e.g., contact created, invoice updated). This is useful for automating workflows that respond to changes or actions within the Lexware system.
Typical use cases include:
- Automatically notifying external systems when a new contact is created.
- Triggering downstream processes when an invoice is updated or deleted.
- Integrating Lexware events into broader automation pipelines via webhooks.
For example, you could configure this node to send a webhook notification to your CRM whenever a new article is created in Lexware, keeping your product catalog synchronized.
Properties
| Name | Meaning |
|---|---|
| Event Type | The type of Lexware event to trigger on. Options: Contact Created, Contact Updated, Contact Deleted, Invoice Created, Invoice Updated, Invoice Deleted, Article Created, Article Updated, Article Deleted. |
| Webhook URL | The URL where webhook notifications will be sent when the specified event occurs. |
| Webhook Secret | An optional secret key used to secure webhook notifications, ensuring authenticity. |
Output
The node outputs JSON data representing the result of the triggered event or the webhook setup confirmation. The output structure typically includes details about the event that occurred and any response from the Lexware API related to the webhook trigger.
No binary data output is indicated for this trigger 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.
- The webhook URL provided must be accessible by Lexware to receive event notifications.
- Optional webhook secret enhances security by allowing verification of incoming webhook requests.
Troubleshooting
- Missing Required Fields Error: If required parameters for the trigger operation are not provided, the node throws an error listing missing fields. Ensure all mandatory properties (Event Type, Webhook URL) are set.
- Webhook Delivery Failures: If the webhook URL is unreachable or returns errors, events may not be delivered. Verify the webhook endpoint is correct and publicly accessible.
- Authentication Errors: Invalid or missing API keys will cause authentication failures. Confirm that the API key credential is correctly configured.
- Security Mismatch: If a webhook secret is set, ensure the receiving endpoint validates it properly; otherwise, webhook calls might be rejected or ignored.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and event types)
- n8n Webhook Node Documentation (for setting up receiving endpoints)
- Webhook Security Best Practices (general guidelines on securing webhooks)
This summary is based solely on static analysis of the provided source code and property definitions for the Trigger resource and Trigger operation.