Actions12
消息 → 消息已读未读查询
AI-generatedOverview
This node interacts with the POPO OpenPlatform Robot API to query the read and unread status of group messages. It is useful for scenarios where you need to track which members of a group have read or not read a specific message, such as in team communication or notification systems. For example, it can be used to generate reports on message engagement or to trigger follow-up actions based on unread messages.
Use Case Examples
- Query the list of users who have read a particular group message to confirm receipt.
- Retrieve the list of users who have not read a message to send reminders or alerts.
Properties
| Name | Meaning |
|---|---|
| msgId | The unique identifier of the message to query. |
| sessionType | The type of session; only supports group messages fixed as '3'. |
| type | The type of query: read list (1) or unread list (2). |
| st | The timestamp cutoff for the query. |
| page | The page number for paginated results, default is 1. |
| size | The number of results per page, default is 30. |
Output
JSON
data- The response data containing the read or unread details of the message.
Dependencies
- Requires an API key credential for the POPO OpenPlatform Robot API to authenticate requests.
Troubleshooting
- Ensure the msgId is correct and corresponds to a valid group message.
- The sessionType must be '3' as only group messages are supported for this query.
- The 'type' parameter must be either '1' (read list) or '2' (unread list).
- Check that the timestamp 'st' is a valid number representing the cutoff time for the query.
- Pagination parameters 'page' and 'size' should be positive integers; otherwise, the API may return errors or unexpected results.