Lexoffice Event Trigger icon

Lexoffice Event Trigger

Webhook expecting Lexoffice Event Payloads
Join our community

Overview

The Lexoffice Event Trigger node is designed to act as a webhook trigger in n8n, listening for event payloads sent from Lexoffice. When configured, it allows your workflow to react automatically to a wide range of events occurring in your Lexoffice account, such as the creation, update, or deletion of contacts, invoices, credit notes, and more.

Common scenarios:

  • Automatically process new invoices or contacts as soon as they are created in Lexoffice.
  • Sync changes or deletions of business documents (like quotations, vouchers, or delivery notes) with other systems.
  • React to payment status updates or token revocations for integration health monitoring.

Practical examples:

  • When a new invoice is created in Lexoffice, send a notification email or update a CRM.
  • If a contact is deleted, remove or archive the corresponding record in another database.
  • On payment status change, trigger an accounting or reconciliation workflow.

Properties

Name Type Meaning
Events multiOptions Specifies which Lexoffice events should trigger this workflow. You can select one or multiple events from a comprehensive list (e.g., "invoice.created", "contact.changed", etc.), or use "*" to listen to all supported event types.

Output

The node outputs the full JSON body received from Lexoffice when a matching event occurs. The structure of this output depends on the specific event type but will always reflect the original webhook payload sent by Lexoffice.

Example output structure:

{
  "eventType": "invoice.created",
  "resourceId": "1234567890abcdef",
  // ...other fields as provided by Lexoffice
}
  • The output is always in the json field of the n8n item.
  • No binary data is produced by this node.

Dependencies

  • External Service: Requires Lexoffice to be configured to send webhooks to the URL provided by this n8n node.
  • No API keys or authentication are required for this node itself, but Lexoffice must be able to reach your n8n instance (publicly accessible endpoint).

Troubleshooting

  • No Data Received:
    • Ensure that Lexoffice is correctly configured to send webhooks to your n8n instance's public URL.
    • Make sure the selected events in the node match those being sent by Lexoffice.
  • Empty Output:
    • This may occur if the incoming event type does not match any of the selected events, or if the payload is missing the eventType property.
  • Webhook Not Triggering:
    • Check network/firewall settings to ensure Lexoffice can reach your n8n webhook endpoint.
    • Verify that the node is active and the workflow is enabled in n8n.

Links and References

Discussion