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 retrieve all "Trigger" resources. Specifically, the "Get All" operation fetches a list of trigger events configured in Lexware Office. This is useful for workflows that need to monitor or react to various webhook event types from Lexware Office, such as contact creation, invoice updates, or article changes.
Common scenarios include:
- Automating notifications or actions when specific events occur in Lexware Office.
- Synchronizing data between Lexware Office and other systems based on triggered events.
- Monitoring webhook configurations programmatically.
Example: Fetching all webhook triggers to audit which events are currently subscribed to and their webhook URLs.
Properties
| Name | Meaning |
|---|---|
| Return All | Boolean flag to return all results or limit the number of results returned. |
| Limit | Maximum number of results to return when "Return All" is false (1 to 250). |
| Page | Zero-based page number for paginated results when "Return All" is false. |
| Sort | Sort order for results. Options include: - Created At (Ascending/Descending) - Updated At (Ascending/Descending) - Voucher Date (Ascending/Descending) - Name (Ascending/Descending) - ID (Ascending/Descending) |
| Cursor | Cursor string for cursor-based pagination (optional). |
| Offset | Offset number for offset-based pagination (optional). |
Output
The output is a JSON array where each item represents a trigger resource retrieved from Lexware Office. Each item contains details about a webhook event subscription, including event type, webhook URL, and optional security secret.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the Lexware Office API base URL configured in the credentials.
- No additional external dependencies beyond the Lexware Office API.
Troubleshooting
- Missing Required Fields Error: If required parameters for the operation are not provided, the node throws an error listing missing fields. Ensure all mandatory inputs are set.
- API Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify the API key and resource URL in the credentials.
- Pagination Issues: When not returning all results, ensure the
Limit,Page,Cursor, andOffsetparameters are correctly set to avoid incomplete or empty responses. - Network or API Errors: General HTTP errors from the Lexware Office API may occur; check network connectivity and API status.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and webhook triggers)
- n8n documentation on Using Credentials
- n8n documentation on Pagination Handling
If you need details on other operations or resources, feel free to ask!