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 enables interaction with the Lark messaging platform, specifically managing message files. The "Upload Files" operation allows users to upload files to Lark Messenger, which can be useful for automating file sharing within chats or channels in Lark. This is beneficial in scenarios such as sending reports, images, or documents automatically as part of a workflow.
For example, a user might automate uploading daily sales reports to a team chat or share images generated by another system directly into a Lark conversation.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: Tenant Token, OAuth2 |
| Use Custom Body | Boolean flag indicating whether to send a custom JSON body instead of the default format |
| Custom Body | JSON object representing a custom request body to send when "Use Custom Body" is enabled |
- Authentication: Choose between two authentication methods to authorize the API calls.
- Use Custom Body: When enabled, allows the user to specify a fully custom JSON payload for the upload request.
- Custom Body: The actual JSON content sent as the request body if "Use Custom Body" is true.
Output
The node outputs data in JSON format representing the response from the Lark API after attempting to upload files. This typically includes metadata about the uploaded file(s), such as file IDs, URLs, or status information confirming successful upload.
If binary data is involved (e.g., the file content itself), it would be handled internally but not explicitly detailed here.
Dependencies
- Requires valid authentication credentials for Lark API access, either via a tenant token or OAuth2.
- Needs network access to
https://open.larksuite.com/open-apis. - No additional external dependencies beyond standard HTTP requests and authentication.
Troubleshooting
- Authentication errors: Ensure that the selected authentication method is correctly configured with valid tokens or OAuth credentials.
- Invalid custom body: If using a custom JSON body, verify its structure matches the expected API schema; malformed JSON will cause request failures.
- File size or type restrictions: The Lark API may impose limits on file sizes or types; exceeding these will result in errors.
- Network issues: Connectivity problems or incorrect base URL configuration can prevent successful uploads.
Common error messages will relate to authorization failures, invalid request payloads, or server-side validation errors. Reviewing the API response details usually helps identify the root cause.