Mark as Read
AI-generatedSummary
Mark an incoming WhatsApp message as read to notify the sender that the message has been seen, using the GoFlow WhatsApp API.
Inputs
- To (required) — The recipient identifier, which can be a phone number (e.g., 77009876543) or a group ID (e.g., ...@g.us). Typically obtained from the incoming event's chat_id.
- Message ID (required) — The ID of the incoming message to mark as read.
- API Key Override — Optional per-item API key override allowing one flow to manage multiple numbers. Leave empty to use the credential's API key.
- Delay Before Action — Optional delay before marking the message as read to simulate human behavior. Can be none, fixed duration, or random duration within specified bounds.
- Delay (Sec) — If Delay Before Action is fixed, the fixed number of seconds to delay.
- Delay Min (Sec) — If Delay Before Action is random, the minimum number of seconds to wait before action.
- Delay Max (Sec) — If Delay Before Action is random, the maximum number of seconds to wait before action.
Output shape
A list of items each containing a JSON response from the GoFlow WhatsApp API indicating the success or failure of marking the corresponding message as read.
If the operation completes successfully, the API returns 'ok' indicating that the message has been marked as read on the GoFlow side. UI indications such as blue ticks on recipients' devices depend on their settings (e.g., read receipts) and device behavior — lack of a blue tick is not considered a failure of the node or operation.