Overview
This node listens for various Lexware Office events via webhooks, enabling automation workflows to trigger when specific business-related events occur. It is useful for integrating Lexware Office with other systems by reacting to changes such as contact creation or updates, invoice lifecycle events, payment processing, document uploads, and more.
Common scenarios include:
- Automatically updating CRM records when a contact is created or updated.
- Triggering notifications or accounting processes when invoices are paid or overdue.
- Syncing quotation status changes with sales pipelines.
- Processing payments and updating financial records in real-time.
- Handling file uploads or dunning notices automatically.
For example, you could use this node to start a workflow that sends an email notification whenever a new invoice is created or to update your ERP system when a payment is received.
Properties
| Name | Meaning |
|---|---|
| Event Type | The type of Lexware Office event to listen for. Options include contact, invoice, quotation, article, voucher, payment, file upload, dunning events, or all events (use with caution). |
| Webhook Secret | Optional secret key used to verify the authenticity of incoming webhook requests. Recommended for security. |
| Filter by Contact ID | Restrict triggering to events related to a specific contact ID. Applicable to many contact and invoice-related events. |
| Filter by Voucher Type | Restrict triggering to events related to a specific voucher type such as invoice, quotation, credit note, delivery note, order confirmation, dunning, or down payment invoice. |
| Filter by Status | Restrict triggering to events with a specific status like draft, open, paid, overdue, voided, accepted, rejected, completed, or cancelled. Applies to status change events for invoices, quotations, vouchers, and dunnings. |
| Filter by Amount Range | Filter events by minimum and/or maximum amount and currency. Useful for invoices, quotations, payments, and related events. |
| Filter by Date Range | Filter events occurring within a specified start and end date/time range. |
| Additional Filters | Collection of options including: • Include Metadata: Whether to include extra metadata in the webhook payload (default true). • Include Related Data: Include related entities like contact info. • Retry on Failure: Enable retrying webhook delivery. • Max Retries: Maximum retry attempts. • Retry Delay: Delay between retries in seconds. |
Output
The node outputs JSON data representing the event payload received from Lexware Office, structured as follows:
eventType: The type of event triggered.eventId: Unique identifier for the event.timestamp: ISO timestamp of when the event occurred.data: Object containing event-specific data, e.g., contact details, invoice information, payment details, etc.metadata: Additional metadata about the event source, version, delivery ID, and retry count.
If configured, the output may also include related data (e.g., contact info for invoices) and additional metadata depending on filter settings.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with Lexware Office services.
- The node expects to receive webhook POST requests at a configured endpoint path.
- Uses HMAC SHA256 signature verification for webhook security if a webhook secret is set.
- Requires Node.js crypto module for signature verification (bundled with n8n runtime).
Troubleshooting
- Invalid webhook signature: If the webhook secret is set but the incoming request's signature header does not match the computed HMAC, the node will throw an "Invalid webhook signature" error. Ensure the webhook secret matches exactly between Lexware Office and the node configuration.
- No events triggering: Verify that the selected event type matches the actual events sent by Lexware Office. Also check any filters (contact ID, voucher type, status, amount, date) do not exclude all incoming events unintentionally.
- Retries not working: If webhook delivery fails, ensure "Retry on Failure" is enabled and max retries/delay are properly configured.
- Mock event testing: The node supports generating mock events for manual trigger testing. Use this to verify workflow logic without waiting for real events.
Links and References
- Lexware Office API Documentation (for event types and webhook setup)
- Webhook Security Best Practices
- HMAC SHA256 Explanation