Actions28
- File Actions
- Multipart Upload File Actions
- Permission Member Actions
- Permissionpublic Actions
- Statistic Actions
- Media Actions
- Multipart Upload Media Actions
- Comment Actions
- Subscription Actions
- Document Import Actions
Overview
The node "Lark Files" provides integration with Lark's file management system, specifically enabling operations related to files stored or managed within the Lark platform. The "Download A File" operation allows users to download a file from Lark by specifying a unique file token. This is useful in scenarios where automated workflows need to retrieve files from Lark for processing, archiving, or sharing outside of the Lark environment.
Practical examples include:
- Automatically downloading meeting notes or documents shared in Lark for backup.
- Fetching files uploaded by users in Lark to process them further in other systems.
- Integrating Lark file downloads into larger automation pipelines that handle document workflows.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token (using a tenant-level API token) or OAuth2 (using OAuth2 authentication flow). |
| File Token | The unique token identifying the file to be downloaded. Required to specify which file to fetch. |
| Options | Additional optional settings for the download operation. Currently supports: Use Custom Body (boolean) - whether to send a custom request body. |
Output
The node outputs the downloaded file data in the json output field. Typically, this will contain metadata about the file and the file content itself, depending on how the node handles the response. If the file is binary (e.g., images, PDFs), the node may output the file as binary data suitable for further processing or saving.
Dependencies
- Requires an API authentication credential, either a tenant token or OAuth2 token, configured in n8n.
- Connects to the Lark Suite Open APIs at
https://open.larksuite.com/open-apis. - No additional external dependencies beyond the configured credentials and network access to Lark APIs.
Troubleshooting
- Invalid or missing file token: Ensure the "File Token" property is correctly set and corresponds to a valid file in Lark.
- Authentication errors: Verify that the selected authentication method is properly configured and the token or OAuth2 credentials are valid and have sufficient permissions.
- Network issues: Confirm that n8n can reach the Lark API endpoint and there are no firewall or proxy restrictions.
- Custom body usage: If "Use Custom Body" is enabled, ensure the custom body format matches the API expectations; otherwise, the request may fail.
Links and References
- Lark Files API Overview
- Lark Files Guide - Introduction (for details on obtaining file tokens)