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 query the read status of a specific message. It is useful in scenarios where you need to track which users have read a particular message sent via Lark Messenger, such as monitoring communication engagement or confirming message delivery within teams.
Practical examples include:
- Checking if an important announcement has been read by all intended recipients.
- Auditing message read receipts for compliance or record-keeping.
- Triggering follow-up actions based on whether a message was read.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method used to authenticate API requests. Options: "Tenant Token" or "OAuth2". |
| User Id Type | Category of user ID provided. Optional values: "open_id", "union_id", "user_id". |
| Message Id | The unique identifier of the message whose read status is being queried. (Required) |
| Options | Additional optional settings: • Use Custom Body: Whether to send a custom request body. |
Output
The node outputs JSON data containing the read status information of the specified message. This typically includes details about which users have read the message and possibly timestamps or counts related to read receipts.
If binary data were involved (e.g., attachments), it would be summarized here, but this node focuses on JSON response data from the API.
Dependencies
- Requires access to the Lark Suite Open API endpoint at
https://open.larksuite.com/open-apis. - Needs either a Tenant Token or OAuth2 credentials configured in n8n for authentication.
- Proper permissions/scopes must be granted to the API credentials to query message read statuses.
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 or error responses.
- Incorrect User Id Type may lead to failed queries or empty results.
Error messages:
- 401 Unauthorized: Check that your API credentials are valid and have not expired.
- 404 Not Found: Verify the Message Id is correct and the message exists.
- 400 Bad Request: Ensure all required parameters are correctly set, especially Message Id and User Id Type if used.
Resolving these usually involves verifying credentials, checking input parameters, and ensuring the API permissions are sufficient.