Actions116
- 💬 Chats Actions
- 👤 Contacts Actions
- 👥 Groups Actions
- Get Info Admin Only
- Set Messages Admin Only
- Get Messages Admin Only
- Get Invite Code
- Revoke Invite Code
- Get Participants
- Add Participants
- Remove Participants
- Promote To Admin
- Demote To Admin
- Create Group
- Get Groups
- Join Info Group
- Join Group
- Refresh Groups
- Get Group
- Delete Group
- Leave Group
- Get Chat Picture
- Set Picture
- Delete Picture
- Set Description
- Set Subject
- Set Info Admin Only
- 🖥️ Sessions Actions
- 🆔 Profile Actions
- 🖼️ Screenshot Actions
- 📤 Chatting Actions
- 📢 Channels Actions
- 🟢 Status Actions
- ✅ Presence Actions
- 🏷️ Labels Actions
- 🔍 Observability Actions
- 🔑 Auth Actions
Overview
This node operation sends a 'seen' receipt for a chat message in a messaging session, indicating that the message has been read. It is useful in chat automation workflows where acknowledging message receipt is necessary, such as in customer support bots or chat monitoring systems.
Use Case Examples
- Marking incoming messages as seen to update the chat status in a customer support system.
- Automatically sending read receipts in a chatbot to inform users their messages have been acknowledged.
Properties
| Name | Meaning |
|---|---|
| Session | The session identifier for the chat connection, used to specify which chat session to send the seen receipt for. |
| Chat Id | The identifier of the chat where the message was received, specifying the target chat for the seen receipt. |
| Message Id | The identifier of the specific message to mark as seen, important for marking all messages as seen in the NOWEB engine. |
| Participant | The ID of the user who sent the message, used in group chats to specify the message sender (undefined for individual chats). |
| Request Options | Additional options for the request such as batching, SSL certificate validation, proxy settings, and timeout configuration. |
Output
JSON
success- Indicates whether the 'seen' receipt was successfully sent.messageId- The ID of the message that was marked as seen.chatId- The ID of the chat where the message was marked as seen.
Dependencies
- Requires an active chat session and connection to the messaging service API, authenticated via session credentials.
Troubleshooting
- Common issues include invalid session or chat IDs causing failures to send the seen receipt.
- Timeout errors may occur if the server does not respond within the configured timeout period; increasing the timeout or checking network connectivity can help.
- SSL certificate validation errors can be bypassed by enabling the 'Ignore SSL Issues' option, but this reduces security.