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 node "Lark Messenger" provides integration with the Lark messaging platform, allowing users to manage messages and reactions within Lark Messenger. Specifically, the operation Delete A Reaction For A Message enables users to remove a specific reaction from a message by specifying the message ID and the reaction ID.
This node is beneficial in scenarios where automated moderation or cleanup of message reactions is needed, such as removing inappropriate reactions, managing user feedback, or resetting reactions after an event.
Example use case:
- Automatically deleting a reaction added by mistake on a message in a team chat.
- Removing all reactions from a message after a poll has ended.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| Message Id | The unique identifier of the message from which the reaction will be deleted. |
| Reaction Id | The unique identifier of the reaction to be deleted from the specified message. |
| Options | Additional optional settings: |
| - Use Custom Body | Boolean flag indicating whether to send a custom request body instead of the default. |
Output
The node outputs JSON data representing the result of the delete reaction API call. Typically, this includes confirmation of successful deletion or error details if the operation failed.
No binary data output is involved in this operation.
Dependencies
- Requires access to the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis. - Requires valid authentication credentials, either:
- A Tenant Token credential, or
- An OAuth2 credential.
- Proper configuration of these credentials in n8n is necessary for successful API calls.
Troubleshooting
Common issues:
- Invalid or expired authentication tokens leading to authorization errors.
- Incorrect or non-existent message ID or reaction ID causing "not found" errors.
- Network connectivity issues preventing API communication.
Error messages and resolutions:
- 401 Unauthorized: Check that the authentication token is valid and has not expired.
- 404 Not Found: Verify that the message ID and reaction ID are correct and exist.
- 400 Bad Request: If using a custom body, ensure the JSON structure matches API expectations.
- Network errors: Confirm internet connectivity and that the Lark API endpoint is reachable.
Links and References
- Lark Open Platform Documentation (general API reference)
- Lark Messenger API Reference (for message and reaction management)