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 retrieve files stored in the system. Specifically, the "File" resource with the "Get All" operation allows users to fetch multiple files based on various filtering criteria such as file type, category, content type, access level, processing status, date ranges, and more.
Common scenarios where this node is beneficial include:
- Automating document management workflows by retrieving all invoices or contracts within a specific date range.
- Filtering and downloading images or PDFs for further processing or archival.
- Searching files by tags or descriptions to integrate with other systems or trigger notifications.
- Managing access levels and processing statuses of files in bulk.
Practical example:
- A user wants to get all PDF invoices created in the last month that are publicly accessible and have completed processing status. They can configure the node with appropriate filters (fileType: PDF, category: invoices, startDate/endDate, accessLevel: public, processingStatus: completed) and retrieve the matching files for further automation.
Properties
| Name | Meaning |
|---|---|
| File Type | Type of file to filter by. Options: Invoice, Credit Note, Quotation, Delivery Note, Dunning, Receipt, Voucher, Image, PDF, Contract, Other. |
| Category | Category of file to filter by. Options: Sales, Purchase, Financial, Administrative, Invoices, Receipts, Contracts, Images, Scans, Documents. |
| Content Type | MIME type to filter by (e.g., image/jpeg, application/pdf). |
| Access Level | Access level to filter by. Options: All, Private, Public, Restricted. |
| Processing Status | Processing status to filter by. Options: All, Pending, Processing, Completed, Failed. |
| E-Invoice Only | Boolean flag to filter for e-invoice files only. |
| Search Term | Search files by description or tags (text search). |
| Start Date | Start date for filtering files (format YYYY-MM-DD). |
| End Date | End date for filtering files (format YYYY-MM-DD). |
| Archived Status | Filter by archived status. Options: All Files, Active Only, Archived Only. |
| Return All | Boolean flag indicating whether to return all results or limit the number of results. |
| Limit | Maximum number of results to return when Return All is false. Range: 1 to 250. Default is 50. |
| Page | Page number for pagination (0-based index). |
| Sort | Sort order for results. Options: Created At (Ascending/Descending), Updated At (Ascending/Descending), Voucher Date (Ascending/Descending), Name (Ascending/Descending), ID (Ascending/Descending). Default: Created At Descending. |
| Cursor | Cursor string for cursor-based pagination. |
| Offset | Offset number for offset-based pagination (minimum 0). |
Output
The node outputs an array of JSON objects representing the files retrieved from Lexware Office according to the specified filters.
Each object in the output array corresponds to a file entity with its associated metadata as returned by the Lexware Office API. This typically includes fields such as file ID, name, type, category, content type, access level, processing status, creation and update timestamps, and any other relevant attributes.
If the node is configured to return all results, it returns the full list; otherwise, it limits the output to the specified number of items.
The node does not output binary data directly for this operation; it only returns metadata about the files.
Dependencies
- Requires an API key credential for authenticating with the Lexware Office API.
- The node uses the Lexware Office API base URL provided in the credentials.
- No additional external dependencies are required beyond the API access.
- Proper configuration of the API key and resource URL in n8n credentials is necessary.
Troubleshooting
- Missing Required Fields Error: If required parameters for the operation are missing, the node throws an error listing the missing fields. Ensure all mandatory inputs are provided.
- Authentication Errors: If the API key credential is invalid or missing, authentication will fail. Verify the API key and resource URL in the credentials.
- Pagination Issues: When using pagination parameters like page, limit, cursor, or offset, ensure values are within valid ranges to avoid empty or incomplete results.
- Empty Results: If no files match the filter criteria, the node returns an empty array. Adjust filters or verify data availability.
- API Rate Limits: Excessive requests may be throttled by the API. Respect rate limits configured in the credentials or reduce request frequency.
Links and References
- Lexware Office API Documentation (general reference for API endpoints and parameters)
- MIME Types Reference (for specifying content types)
This summary is based solely on static analysis of the provided source code and property definitions.