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 management capabilities for Lark Messenger, focusing here on the "Download Images" operation under the "Message Image" resource. This operation allows users to download images from messages by specifying an image key. It is useful in scenarios where automated workflows need to retrieve and process images sent or received via Lark Messenger, such as archiving media content, performing image analysis, or integrating with other systems that require image data.
For example, a user might automate downloading all images from certain chat messages to store them in a cloud storage service or trigger further processing like OCR or image recognition.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" (using a tenant API token) or "OAuth2" (using OAuth2 credentials). |
| Image Key | The unique identifier (key) of the image to be downloaded. This is required to specify which image to fetch. |
| Options | Additional optional settings: - Use Custom Body: Whether to send a custom request body when making the API call (boolean). |
Output
The node outputs the downloaded image data in the json output field. Typically, this will include metadata about the image and the binary data representing the image file itself. The binary data can then be used downstream in the workflow for saving to disk, uploading elsewhere, or further processing.
If the node supports binary data output, it will provide the image content in binary form attached to the output item, allowing seamless handling of image files within n8n workflows.
Dependencies
- Requires valid authentication credentials configured in n8n, either:
- A tenant token credential for direct API access.
- An OAuth2 credential for authorized access.
- Access to the Lark Suite Open APIs endpoint (
https://open.larksuite.com/open-apis). - Proper permissions granted to the credentials to read message images.
Troubleshooting
- Invalid or missing Image Key: Ensure the "Image Key" property is correctly set and corresponds to an existing image in Lark Messenger.
- Authentication errors: Verify that the selected authentication method is properly configured and the credentials are valid and have sufficient permissions.
- API rate limits or network issues: If requests fail due to rate limiting or connectivity problems, consider implementing retry logic or checking network/firewall settings.
- Using Custom Body option: If enabled incorrectly, the API request may fail due to malformed request bodies. Use this option only if you know the exact request format required.