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
This node integrates with the Lexware Office API to manage various business resources. Specifically, for the Trigger resource with the Create operation, it allows users to create webhook triggers that listen for specific events in the Lexware system and send notifications to a specified URL.
Typical use cases include automating workflows based on events such as contact creation, invoice updates, or article changes. For example, you can set up a trigger to notify your system whenever a new invoice is created, enabling real-time processing or synchronization with other systems.
Properties
| Name | Meaning |
|---|---|
| Event Type | The type of event to trigger. Options include: 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 | (Optional) A secret key used to secure webhook notifications, ensuring authenticity. |
| Additional Fields | Optional extra fields for the resource, including: Name, Description, Notes, Tags, External ID. |
Output
The node outputs an array of JSON objects representing the result of the create trigger operation. Each object corresponds to the created trigger resource returned by the Lexware Office API.
The output json field contains details about the newly created trigger, such as its identifier and configuration.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the Lexware Office API base URL from the provided credentials.
- Proper network access to the Lexware Office API endpoint is necessary.
- The user must configure the webhook URL to receive incoming HTTP requests from Lexware.
Troubleshooting
- Missing Required Fields Error: If required parameters like
eventTypeorwebhookUrlare not provided, the node throws an error listing missing fields. Ensure all mandatory inputs are filled. - Authentication Errors: Invalid or missing API key credentials will cause authentication failures. Verify that the API key is correct and has sufficient permissions.
- Webhook Delivery Failures: If the webhook URL is unreachable or rejects requests, no notifications will be received. Confirm the webhook endpoint is publicly accessible and correctly configured.
- Secret Mismatch: If a webhook secret is set, ensure the receiving endpoint validates it properly; otherwise, security checks may fail.
Links and References
- Lexware Office API Documentation (official API docs)
- Webhook Security Best Practices (general webhook security guidelines)
If you need further details on other operations or resources, feel free to ask!