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 manage various business resources such as contacts, articles, invoices, vouchers, and recurring templates. Specifically, for the Recurring Template resource with the Update operation, the node updates an existing recurring template in the Lexware system.
Use cases include automating updates to recurring billing templates, adjusting descriptions, notes, tags, or external IDs associated with these templates. This is beneficial for businesses that need to programmatically maintain their recurring invoice or quotation templates without manual intervention.
Example: Automatically update the description or tags of a recurring invoice template when certain conditions are met in your workflow.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to update on the recurring template: |
| - Name | The name of the recurring template |
| - Description | A textual description of the recurring template |
| - Notes | Additional notes related to the recurring template |
| - Tags | Comma-separated tags for categorization or filtering |
| - External ID | An external identifier for integration with other systems |
These properties allow flexible updating of metadata and descriptive information for the recurring template.
Output
The node outputs a JSON array where each element corresponds to the result of the update operation for each input item. The JSON structure reflects the updated recurring template data returned by the Lexware Office API.
If the operation fails for any item and "Continue On Fail" is enabled, the output will include an error object with the error message for that item.
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 API to be configured in the credentials.
- No additional external dependencies beyond the Lexware API and its authentication.
Troubleshooting
- Missing Required Fields Error: If required fields for the update operation are missing, the node throws an error listing those fields. Ensure all mandatory parameters (like the recurring template ID) are provided.
- Authentication Errors: Invalid or missing API keys will cause authentication failures. Verify that the API key credential is correctly set up.
- API Rate Limits: The Lexware API may enforce rate limits; if exceeded, requests might fail. Adjust the workflow frequency or handle retries accordingly.
- Invalid Field Values: Providing invalid values for fields like status or recurrence type may cause API errors. Validate inputs against allowed options.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and data models)
- n8n Documentation on Creating Custom Nodes
- Lexware recurring templates concept: Typically used for automating periodic document generation such as invoices or quotations.
This summary focuses on the "Recurring Template" resource with the "Update" operation, describing how the node updates recurring templates via the Lexware Office API using specified additional fields.