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 the Lark messaging platform, specifically enabling management of messenger resources such as message images. The "Upload Images" operation under the "Message Image" resource allows users to upload images to be used in messages within Lark.
This node is beneficial for automating workflows that involve sending rich media content via Lark Messenger, such as sharing product photos, event flyers, or any visual information directly through automated processes.
Practical examples include:
- Automatically uploading and attaching images from an external source to Lark chat messages.
- Integrating image uploads into customer support workflows where screenshots or photos need to be shared.
- Bulk uploading images for announcements or marketing campaigns within Lark groups.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: "Tenant Token" or "OAuth2". |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body instead of the default format. |
| Custom Body | A JSON object representing a custom request body to send when "Use Custom Body" is true. |
Output
The node outputs data in JSON format containing the response from the Lark API after attempting to upload images. This typically includes metadata about the uploaded images such as URLs, IDs, or status information confirming successful upload.
If the node supports binary data (not explicitly shown here), it would represent the actual image files or related binary content; however, based on the provided code and properties, the output focuses on JSON responses describing the upload result.
Dependencies
- Requires valid authentication credentials for Lark API access, either via a Tenant Token or OAuth2 token.
- Needs network connectivity to
https://open.larksuite.com/open-apis. - No additional external dependencies are indicated beyond standard HTTP requests to the Lark API.
Troubleshooting
- Authentication Errors: If the node fails due to authentication, verify that the correct credential type is selected and that the token or OAuth2 credentials are valid and have not expired.
- Invalid Custom Body: When using the "Use Custom Body" option, ensure the JSON provided is correctly formatted and matches the expected schema of the Lark API for image uploads.
- API Rate Limits: Frequent or bulk uploads may hit API rate limits imposed by Lark. Monitor error messages indicating rate limiting and implement retries or backoff strategies.
- Network Issues: Connectivity problems to the Lark API endpoint will cause failures. Check network settings and firewall rules if errors occur.