Actions10
- Contacts Endpoint Actions
- Invoices Endpoint Actions
- Files Endpoint Actions
Overview
The LexOffice node's "Files Endpoint" resource with the "Download a File" operation allows you to download a file from LexOffice by specifying its Document File ID. This is particularly useful for automating workflows where you need to retrieve documents (such as invoices, receipts, or other files) stored in LexOffice and process them further within n8n or send them to other systems.
Practical examples:
- Automatically downloading invoice PDFs after they are generated in LexOffice.
- Fetching attached documents for archiving or backup purposes.
- Integrating LexOffice file downloads into document management or approval workflows.
Properties
| Name | Type | Meaning |
|---|---|---|
| Document File ID | String | The unique identifier of the document file to download. Required to fetch the file. |
Output
- The node returns the file as binary data.
- The output will include a binary property containing the downloaded file, which can be used in subsequent nodes (e.g., to email, store, or process the file).
- The
jsonfield may contain metadata about the operation, but the main result is the binary file content.
Dependencies
- External Service: Requires access to the LexOffice API.
- Credentials: You must configure the
lexOfficeApicredential in n8n with your LexOffice API key/token. - n8n Configuration: No special environment variables are required beyond standard credential setup.
Troubleshooting
Common Issues:
- Invalid Document File ID: If the provided Document File ID does not exist or is incorrect, the node will return an error indicating that the file could not be found.
- Authentication Errors: If the LexOffice API credentials are missing or invalid, you may receive authentication or authorization errors.
- File Not Available: If the file has been deleted or is not accessible due to permissions, the node will fail to download it.
Error Messages & Resolutions:
"404 Not Found": Check that the Document File ID is correct and exists in your LexOffice account."401 Unauthorized": Ensure your LexOffice API credentials are correctly set up in n8n."403 Forbidden": Verify that your API user has permission to access the requested file.