Actions38
- Message Actions
- Message Buzz Message Actions
- Message Batch Message Actions
- Message Image Actions
- Message File Actions
- Message Message Card Actions
- Message Message Reaction Actions
- Group Actions
- Group Group Member Actions
- Group Group Announcement Actions
Overview
The "Lark Messenger" node provides integration with Lark's messaging platform, specifically enabling management of message files. The "Download Files" operation under the "Message File" resource allows users to download files associated with messages in Lark Messenger.
This node is useful when automating workflows that require retrieving and processing files sent or received via Lark Messenger. For example, a user might want to automatically download attachments from chat messages for archival, analysis, or further processing in other systems.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| File Key | The unique identifier (key) of the file to be downloaded. This is required. |
| Options | Additional optional settings: |
| - Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default one. |
Output
The node outputs the downloaded file data. Typically, this will be binary data representing the contents of the requested file. The output can then be used downstream in the workflow for saving to disk, uploading elsewhere, or processing.
The json output field may contain metadata about the file or the download status, but the primary output is the binary content of the file itself.
Dependencies
- Requires an API authentication token, either a Tenant Token or OAuth2 credentials configured in n8n.
- Connects to Lark Suite's Open APIs at
https://open.larksuite.com/open-apis. - No additional external dependencies beyond the configured credentials and network access to Lark's API.
Troubleshooting
- Invalid or missing File Key: Ensure the "File Key" property is correctly set and corresponds to an existing file in Lark Messenger.
- Authentication errors: Verify that the selected authentication method is properly configured and the credentials are valid.
- Network issues: Confirm that n8n has internet access and can reach Lark's API endpoint.
- Use Custom Body option: If enabled incorrectly, it may cause malformed requests; only enable if you intend to customize the request payload.
Common error messages will relate to authorization failures, invalid parameters, or file not found errors. Checking the input properties and credentials usually resolves these.