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, files, and more. Specifically for the File resource with the Update operation, it enables updating metadata or attributes of an existing file in the Lexware system.
Typical use cases include:
- Updating file details like name, description, notes, tags, or external IDs.
- Managing document metadata in automated workflows.
- Synchronizing file information between Lexware and other systems.
For example, a user might update the description or tags of a file after processing it in another system, ensuring that the Lexware records stay current.
Properties
| Name | Meaning |
|---|---|
| File ID | The unique identifier of the file to update (required). |
| Additional Fields | A collection of optional fields to update on the file: |
| - Name: New name of the file. | |
| - Description: Description text for the file. | |
| - Notes: Additional notes related to the file. | |
| - Tags: Comma-separated tags for categorization. | |
| - External ID: An external system identifier for the file. |
Output
The node outputs a JSON array where each element represents the updated file resource returned from the Lexware Office API after the update operation.
- The
jsonoutput contains the updated file's data including any changed properties. - There is no indication that binary data is output by this operation.
Example output snippet (conceptual):
[
{
"id": "file-id-123",
"name": "Updated File Name",
"description": "Updated description",
"tags": "tag1,tag2",
"externalId": "ext-456",
...
}
]
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 other external dependencies are indicated.
Troubleshooting
- Missing Required Fields Error: If required parameters like
File IDare not provided, the node throws an error listing missing fields. Ensure all mandatory inputs are set. - Authentication Errors: Invalid or missing API credentials will cause authentication failures. Verify that the API key credential is correctly configured.
- API Request Failures: Network issues or incorrect base URL settings can cause request errors. Confirm connectivity and credential configuration.
- Continue On Fail Behavior: If enabled, the node will continue processing subsequent items even if one fails, returning error messages in the output JSON.
Links and References
- Lexware Office API Documentation (general reference for API capabilities)
- n8n Documentation on Creating Custom Nodes
This summary focuses on the File resource's Update operation as requested, based on static analysis of the provided source code and property definitions.