Actions53
- Account Actions
- Contact Actions
- Group Actions
- Message Actions
- Session Actions
Message → Mark as Read
AI-generatedOverview
This node operation marks a specific WhatsApp message as read using the WasenderAPI. It is useful in scenarios where you want to programmatically update the read status of messages, such as automating message handling workflows or integrating with customer support systems to track message read receipts.
Use Case Examples
- Automatically mark incoming messages as read after processing them in a workflow.
- Mark specific messages as read based on user actions or external triggers.
Properties
| Name | Meaning |
|---|---|
| Session | Selects the WhatsApp session to use for the operation. It can be chosen from a list or specified by ID. If not provided, the session from the incoming item is used automatically. |
| Message Key | A JSON object representing the unique key of the message to mark as read. This includes properties like message ID, remoteJid, and fromMe. |
| Options | Additional request options such as retry behavior and maximum retry attempts for the API request. |
Output
JSON
json- The JSON response from the WasenderAPI after marking the message as read, indicating success or failure of the operation.
Dependencies
- WasenderAPI service with an API key credential
Troubleshooting
- Ensure the session ID is correctly provided or available in the incoming item; otherwise, the node will throw a 'Session is required' error.
- The 'Message Key' must be a valid JSON object representing the message to mark as read; invalid or missing keys will cause errors.
- API request failures may occur due to network issues or invalid session states; enabling retry options can help mitigate transient errors.