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 manage various business resources, including files. Specifically, for the File resource with the Create operation, it allows users to create new file records in the Lexware system. This can be useful for automating document management workflows such as uploading invoices, contracts, or other business-related documents into Lexware directly from an n8n workflow.
Practical examples include:
- Automatically creating a file record when a new invoice PDF is generated.
- Uploading scanned receipts or contracts to Lexware for centralized storage.
- Adding metadata like tags or descriptions to files for better organization.
Properties
| Name | Meaning |
|---|---|
| Additional Fields | A collection of optional fields to add metadata to the file resource: |
| - Name | Name of the file resource |
| - Description | Description of the file |
| - Notes | Additional notes related to the file |
| - Tags | Tags associated with the file (comma-separated) |
| - External ID | External identifier for the file resource |
These properties allow customization and enrichment of the file record being created.
Output
The node outputs JSON data representing the response from the Lexware Office API after creating the file resource. The output typically includes details of the newly created file such as its ID, name, description, tags, and any other metadata returned by the API.
If the node supports binary data output for files (not explicitly shown in the provided code), it would represent the actual file content or downloadable links. However, based on the static analysis, this node primarily handles JSON metadata about files.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node expects the Lexware Office API base URL and API key to be configured in the credentials.
- No additional external dependencies are indicated beyond the Lexware Office API.
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 inputs are set.
- Authentication Errors: Incorrect or missing API key credentials will cause authentication failures. Verify that the API key and base URL are correctly configured.
- API Rate Limits: The node may be subject to API rate limits configured in Lexware. Adjust the rate limit settings if encountering throttling errors.
- Invalid Field Values: Providing invalid values for fields like tags or dates may result in API errors. Validate input formats before execution.
Links and References
- Lexware Office API Documentation (official API docs for reference)
- n8n Documentation (for general usage of custom nodes and credentials)
This summary is based solely on static analysis of the provided source code and property definitions.