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
This node interacts with the Lark Messenger API to obtain a specific reaction for a given message. It is useful in scenarios where you want to retrieve details about how users have reacted to messages within Lark Messenger, such as fetching emoji reactions or other reaction types on a particular message.
Practical examples include:
- Monitoring user engagement by checking reactions on announcements or important messages.
- Automating workflows based on specific reactions (e.g., triggering actions when a "thumbs up" reaction is added).
- Aggregating reaction data for reporting or analytics purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Tenant Token" or "OAuth2". |
| Reaction Type | The type of reaction to query for the message (e.g., emoji name). |
| Message Id | The unique identifier of the message whose reaction is to be obtained (required). |
| Options | Additional options; currently supports "Use Custom Body" to specify if a custom request body should be used. |
Output
The node outputs JSON data representing the reaction information retrieved from the Lark Messenger API for the specified message and reaction type. This typically includes details such as the reaction type, users who reacted, timestamps, and any metadata provided by the API.
If binary data were involved (not indicated here), it would represent attachments or media related to the reaction, but this node focuses on JSON response data only.
Dependencies
- Requires access to the Lark Messenger API.
- Requires an API authentication token, which can be provided via either a Tenant Token credential or OAuth2 credential configured in n8n.
- The base URL for API requests is
https://open.larksuite.com/open-apis. - Proper permissions/scopes must be granted to the credentials to read message reactions.
Troubleshooting
- Common issues:
- Invalid or expired authentication tokens will cause authorization errors.
- Providing an incorrect or non-existent Message ID will result in not found errors.
- Specifying an unsupported or misspelled Reaction Type may return empty results or errors.
- Error messages:
- Authorization errors: Check that the API credentials are valid and have required scopes.
- 404 Not Found: Verify the Message ID is correct and the message exists.
- 400 Bad Request: Ensure the Reaction Type parameter is correctly formatted and supported.
- To resolve these, verify credentials, confirm message IDs, and double-check reaction type values.
Links and References
- Lark Open Platform Documentation
- Lark Messenger API Reference (for message reactions)