How to mark as read in WhatsApp Business

Mark as Read in WhatsApp Business — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Inbound Message ID (wamid) message_id	string	Required	–

Sample request

{
  "message_id": "{{trigger.message_id}}"
}

Returns

{
  "success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Mark as Read.

What does the Mark as Read action do in WhatsApp Business?

Sends a read receipt for an inbound WhatsApp message, surfacing the blue double-checks to the sender. Good practice for human-agent handoff UX.

What inputs does Mark as Read require?

Required: Inbound Message ID (wamid). Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if WhatsApp Business returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Mark as Read support batch operations?

Yes. Run Mark as Read inside a Loop node to process arrays. TinyCommand handles WhatsApp Business's rate limits automatically so you don't have to throttle manually.

More actions