# Check the delivery status of a message in Zapier

> Look up whether a WhatsApp message you sent from a Zap was delivered, read or failed, and send a fallback when it did not arrive.

The **Get Delivery Status of a Message** action of the WhatsAble app looks up a message you sent and returns its status: sent, delivered, read, or failed. It does not send anything.

Use it for a fallback: when a message did not arrive, for example because the number is not on WhatsApp, send an email or alert your team instead. This page is the how-to guide. For the account connection, see the [Zapier overview](/integration/zapier).

## When to use it

- **Email fallback**: 
Send the same information by email when the WhatsApp message failed.

- **Clean your lists**: 
Flag a lead in your CRM when its number cannot receive WhatsApp messages.

## Set up the action

**Send the message first**

The Zap needs a **WhatsAble: [Send WhatsApp Message](/integration/zapier/send-message)** step before this one. That step returns the `message_id` this action needs.

**Wait for WhatsApp**

Add a **Delay by Zapier** step after the send, for example **Delay For** 5 minutes. WhatsApp reports delivery a little after the send, so a check right away usually still shows `sent`.

**Add the WhatsAble action**

Click **+**, search for **WhatsAble**, and choose **Get Delivery Status of a Message** as the **Action event**. Under **Account**, choose the same WhatsAble connection that sent the message.

**Map the message ID**

<img src="/images/zapier-delivery-status-1.webp" alt="Message ID field holding a WhatsApp message ID that starts with wamid." style={{ maxWidth: "480px" }} />

*The only field: the WhatsApp message ID*

**Message ID** `text` (required)

The WhatsApp message ID, which starts with `wamid.`. Map `message_id` from the Send WhatsApp Message step.

**Branch on the status**

Add a **Filter by Zapier** or **Paths by Zapier** step on `status`. Continue your main flow when it is `delivered` or `read`. Send the fallback when it is `failed`.

## What the step returns

| Field | Meaning |
| --- | --- |
| `status` | `pending`, `sent`, `delivered`, `read`, or `failed` |
| `message_id` | The WhatsApp message ID you looked up |
| `send_time` | When WhatsAble recorded the message, as a Unix time in milliseconds |
| `delivered_time` | When the message was delivered, in milliseconds, or empty |
| `read_time` | When the contact read the message, in milliseconds, or empty |
| `phone_number` | The contact's number, digits only |
| `send_by` | What sent the message |
| `system_user` | The name of the person who sent the message, or empty |

> [!NOTE]
>
> A message that was never delivered can stay on `sent`. WhatsApp sets `read` only when the contact has read receipts turned on, so `delivered` is the safe sign that the message arrived.

## Limits

- The action finds only messages sent from the WhatsApp number of the connection's API key. For any other ID, the step fails with "No message with this id was sent from this API key's WhatsApp number."
- It does not work with [Schedule a Follow-Up Message](/integration/zapier/schedule-message): that action returns no message ID, because the message is not sent yet.
- It does not return the reason a message failed, only the `failed` status.

## Troubleshooting

<details>
<summary>No message with this id was sent from this API key's WhatsApp number</summary>

Check that you mapped `message_id` from a Send WhatsApp Message step, and that both steps use the same WhatsAble connection.

</details>

<details>
<summary>The status is always sent</summary>

The check ran before WhatsApp reported delivery. Make the delay longer.

</details>