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 allowing users to update app messages within message cards. This operation is useful when you want to programmatically modify the content of an existing message sent via a Lark app, such as correcting information, updating status, or enhancing message details dynamically.
Practical examples include:
- Updating a notification message in a team chat after a task status changes.
- Modifying a message card content to reflect new data fetched from another system.
- Correcting typos or adding additional context to previously sent messages.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests. Options: Tenant Token, OAuth2 |
| Message Id | The unique identifier of the message to be updated (required) |
| Content | The new textual content to replace the existing message content |
| Custom Body | A JSON object representing a custom request body to send instead of the default content format |
| Options > Use Custom Body | Boolean flag indicating whether to use the Custom Body property instead of the Content field |
Output
The node outputs JSON data representing the response from the Lark API after attempting to update the message. This typically includes confirmation of success or failure and any relevant metadata about the updated message.
If binary data were involved (not indicated here), it would represent attachments or media related to the message, but this node focuses on JSON content updates only.
Dependencies
- Requires valid authentication credentials for the Lark API, either via a Tenant Token or OAuth2 token.
- Needs network access to
https://open.larksuite.com/open-apis. - Proper configuration of credentials in n8n is necessary to authorize API calls.
Troubleshooting
- Invalid Message Id: If the provided message ID does not exist or is incorrect, the API will return an error. Verify the message ID before running the node.
- Authentication Errors: Using invalid or expired tokens will cause authorization failures. Ensure that the selected authentication method is correctly configured and tokens are valid.
- Malformed Custom Body: When using the "Use Custom Body" option, ensure the JSON structure matches the expected API schema; otherwise, the request may fail.
- API Rate Limits: Frequent updates might hit rate limits imposed by Lark API. Implement retries or backoff strategies if needed.