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, enabling users to manage various business resources such as contacts, articles, invoices, vouchers, and recurring templates. Specifically, for the Recurring Template resource with the Create operation, it allows users to create new recurring templates in their Lexware Office system.
This is useful in scenarios where businesses want to automate the creation of recurring billing or document templates, such as monthly invoices or regular quotations, ensuring consistent and repeatable document generation without manual intervention.
Practical example:
A company that issues monthly subscription invoices can use this node to create a recurring invoice template that automatically generates invoices every month based on predefined settings like name, description, tags, and external IDs.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to specify extra details about the recurring template: |
| - Name: Name of the recurring template | |
| - Description: Description of the recurring template | |
| - Notes: Additional notes related to the template | |
| - Tags: Tags associated with the template (comma-separated) | |
| - External ID: An external identifier for the template |
These additional fields allow customization of the recurring template's metadata during creation.
Output
The node outputs a JSON array containing the response from the Lexware Office API after creating the recurring template. The JSON structure corresponds to the created recurring template object returned by the API, which typically includes identifiers, status, metadata (like name, description, tags), recurrence settings, and other relevant details.
No binary data output is indicated for 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.
- No additional external dependencies are required beyond the Lexware Office API access.
Troubleshooting
Missing Required Fields Error:
If required fields for the create operation are not provided, the node throws an error listing missing fields. Ensure all mandatory properties are set before execution.Authentication Errors:
If the API key or resource URL is incorrect or missing, authentication will fail. Verify that the API key credential is correctly configured in n8n.API Rate Limits:
The Lexware Office API may enforce rate limits. If requests are throttled, consider adjusting the API rate limit setting or adding delays between executions.Invalid Field Values:
Providing invalid values (e.g., wrong data types or unsupported tags) may cause API errors. Validate input data according to Lexware Office API specifications.
Links and References
- Lexware Office API Documentation (Please verify the exact URL from official sources)
- n8n Documentation on Creating Custom Nodes
- Lexware Office Official Website
If you need further details on other operations or resources, feel free to ask!