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 manage various business resources such as contacts, articles, invoices, vouchers, and triggers. Specifically for the Trigger resource with the Update operation, this node allows updating webhook trigger configurations that listen for specific events in the Lexware system.
This is useful when you want to programmatically modify webhook triggers to change event subscriptions or update webhook URLs and secrets without manual intervention. For example, you might update a trigger to change the URL where notifications are sent or adjust the secret key used for securing webhook calls.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to update on the trigger resource: |
| - Name | Name of the trigger resource |
| - Description | Description of the trigger resource |
| - Notes | Additional notes related to the trigger |
| - Tags | Tags associated with the trigger (comma-separated) |
| - External ID | External identifier for the trigger resource |
These properties allow you to specify which aspects of the trigger you want to update.
Output
The node outputs an array of JSON objects representing the updated trigger resource(s) returned from the Lexware Office API after the update operation. The exact structure depends on the API response but typically includes details about the trigger such as its ID, event type, webhook URL, secret, and metadata like name, description, tags, and external ID.
No binary data output is indicated for this operation.
Dependencies
- Requires connection credentials to the Lexware Office API, including an API key and resource URL.
- The node uses these credentials to authenticate and send requests to the Lexware Office API endpoints.
- No additional environment variables or external services beyond the Lexware API are required.
Troubleshooting
- Missing Required Fields Error: If required fields for the update operation are not provided, the node throws an error listing missing fields. Ensure all mandatory parameters are set.
- Authentication Errors: If API credentials are invalid or missing, requests will fail. Verify that the API key and resource URL are correctly configured.
- API Endpoint Errors: If the Lexware API is unreachable or returns errors, check network connectivity and API status.
- Webhook URL Validation: Ensure the webhook URL provided is valid and accessible; otherwise, webhook delivery may fail.
- Secret Key Issues: If webhook secret is incorrect or missing, webhook security validation may fail.
Links and References
- Lexware Office API Documentation (Note: Replace with actual API docs link if available)
- n8n Documentation on Creating Custom Nodes
- Webhook Security Best Practices
This summary focuses on the Trigger resource's Update operation within the Lexware Office node, describing how to update webhook trigger settings via the Lexware API using n8n.