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 Office resources programmatically. Specifically, for the Recurring Template resource with the Get operation, the node retrieves detailed information about a single recurring template identified by its unique Template ID.
This functionality is useful in scenarios where you need to fetch and use data from a specific recurring billing or document template within your automation workflows. For example, you might want to retrieve a recurring invoice template's details to generate reports, update other systems, or trigger further processing based on the template's properties.
Properties
| Name | Meaning |
|---|---|
| Template ID | The unique identifier of the recurring template to retrieve. This is a required string input. |
Output
The node outputs a JSON array containing the data of the requested recurring template. The structure of the output JSON corresponds to the recurring template object as defined by the Lexware Office API. It typically includes fields such as template metadata, type, status, recurrence settings, associated contact IDs, category, language, currency, tags, and other relevant attributes describing the recurring template.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the base URL of the Lexware Office API to be configured in the credentials.
- Network connectivity to the Lexware Office API endpoint is necessary.
Troubleshooting
- Missing Required Fields Error: If the "Template ID" is not provided, the node will throw an error indicating missing required fields. Ensure that the Template ID is correctly set.
- Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify that the API key is correctly configured in the node credentials.
- Resource Not Found: If the specified Template ID does not exist, the API may return a not found error. Confirm that the Template ID is correct.
- API Rate Limits: Excessive requests may lead to rate limiting. Adjust the workflow frequency or check API rate limit settings.
- Network Issues: Connectivity problems can cause request failures. Check network access to the Lexware Office API.
Links and References
- Lexware Office API Documentation (official API docs for detailed recurring template schema and usage)
- n8n Documentation (for general usage of the Lexware Office node)
If you need details on other operations or resources, feel free to ask!