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 "Reply To Messages" operation in the Lark Messenger node allows users to send a reply to an existing message within the Lark messaging platform. This is useful for automating conversational workflows, responding to user queries, or integrating chatbots that interact contextually by replying directly to specific messages.
Practical examples include:
- Automatically replying to customer support inquiries with predefined answers.
- Sending follow-up messages in a team chat based on triggers from other systems.
- Creating interactive bots that respond to user commands or questions in a thread.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating API requests; options are "Tenant Token" or "OAuth2". |
| Message Id | The unique identifier of the message to which the reply will be sent. |
| Content | The textual content of the reply message. |
| Msg Type | The type of the message being sent (e.g., text, image). |
| Custom Body | A JSON object allowing full customization of the request body sent to the API. |
| Use Custom Body | Boolean flag indicating whether to use the "Custom Body" property instead of standard fields. |
Output
The node outputs JSON data representing the response from the Lark API after sending the reply message. This typically includes confirmation details such as message IDs, timestamps, and status information. The output does not handle binary data.
Dependencies
- Requires valid authentication credentials: either a Tenant Token or OAuth2 token configured in n8n.
- Depends on access to the Lark Suite Open APIs endpoint (
https://open.larksuite.com/open-apis). - Proper permissions must be granted to the API credentials to send messages and reply to existing ones.
Troubleshooting
- Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or missing Message Id causing the API to reject the request.
- Malformed JSON in the Custom Body causing request failures.
- Error messages:
- Authorization errors usually indicate problems with the provided API credentials; refreshing or reconfiguring them resolves this.
- Validation errors often point to missing required fields like Message Id or invalid message types.
- API rate limits may cause temporary failures; retrying after some time is recommended.