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
This node interacts with the Lark Messenger platform to obtain resource files embedded in messages. Specifically, it allows users to retrieve images or files (including audio and video, but excluding emojis) associated with a particular message by specifying the message ID and the resource key. This is useful for workflows that need to process or archive media content shared within Lark Messenger conversations.
Practical examples include:
- Automatically downloading images or documents shared in team chats for backup or further processing.
- Extracting audio or video files from messages to transcribe or analyze them.
- Integrating Lark Messenger media into other systems like CMS or file storage services.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" or "OAuth2". |
| Type | Resource type to retrieve. Options: "image" (images in messages or rich-text messages), "file" (files, audio, video). |
| Message Id | The unique identifier of the message containing the resource to be fetched. |
| File Key | The key identifying the specific resource file within the message. |
| Options | Additional options for the request. Currently supports: Use Custom Body (boolean) to specify if a custom request body is used. |
Output
The node outputs JSON data representing the requested resource file information retrieved from the Lark Messenger API. This typically includes metadata about the file or image such as URLs, file size, type, and possibly download links.
If the resource is binary (e.g., an image or video file), the node may provide access to the binary data stream or a URL to download the file, enabling subsequent nodes to handle or store the media content.
Dependencies
- Requires valid authentication credentials for Lark Messenger API access, either via a Tenant Token or OAuth2 token.
- Needs network connectivity to
https://open.larksuite.com/open-apis. - Proper configuration of authentication credentials in n8n is necessary before using this node.
Troubleshooting
- Invalid Credentials: Errors related to authentication usually indicate missing or incorrect API tokens. Verify that the correct credential type is selected and configured.
- Resource Not Found: If the message ID or file key is incorrect or the resource does not exist, the API will return an error. Double-check these values.
- Unsupported Resource Type: Using a type other than "image" or "file" may cause failures. Ensure the type matches the resource you want to fetch.
- Network Issues: Connectivity problems can prevent API calls. Confirm internet access and that the Lark API endpoint is reachable.
- Custom Body Usage: If
Use Custom Bodyis enabled but the body is malformed, the request may fail. Validate any custom payloads carefully.