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, allowing users to interact with various Lexware resources such as contacts, articles, invoices, and event subscriptions. Specifically, for the Event Subscription resource with the Get operation, the node retrieves detailed information about a single event subscription by its unique ID.
Typical use cases include:
- Fetching details of a specific event subscription to monitor or audit webhook events.
- Integrating Lexware event subscription data into workflows for further processing or notifications.
- Automating management or reporting of event subscriptions within Lexware Office.
Example: You have an event subscription set up in Lexware Office to notify your system when an invoice is created. Using this node's "Get" operation on Event Subscription, you can retrieve the current configuration or status of that subscription by providing its ID.
Properties
| Name | Meaning |
|---|---|
| Event Subscription ID | The unique identifier of the event subscription to retrieve. This is a required string. |
Output
The node outputs a JSON object representing the details of the requested event subscription. This includes all relevant fields returned by the Lexware Office API for an event subscription, such as its ID, event type, active status, associated contact or voucher types, description, tags, and other metadata.
If multiple items were retrieved (not applicable here since it's a single get), they would be output as an array of JSON objects.
The node does not output binary data for this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the base URL configured in the credentials to send requests.
- No additional external dependencies are needed beyond the Lexware Office API access.
Troubleshooting
- Missing Required Fields Error: If the "Event Subscription ID" is not provided, the node will throw an error indicating missing required fields. Ensure this property is set correctly.
- Authentication Errors: If the API key credential is invalid or missing, the node will fail to authenticate. Verify that the API key and resource URL are correctly configured in the credentials.
- Resource Not Found: If the provided event subscription ID does not exist, the API may return a 404 error. Confirm the ID is correct and exists in your Lexware Office account.
- API Rate Limits: Excessive requests may hit rate limits imposed by Lexware Office. Adjust workflow frequency or handle errors gracefully.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n Documentation - Creating Custom Nodes
- Webhook and Event Subscription Concepts (for understanding event subscriptions)
This summary focuses on the "Event Subscription" resource with the "Get" operation as requested, based on static analysis of the provided source code and input properties.