# Webhook event fields

> Every field Whatsable posts from Settings, Webhooks, which shape includes it, and when the value is empty or missing.

**Settings → Webhooks** posts one JSON object per delivery. The two formats are **Make, Zapier or n8n** and **Your own server**. Neither payload has an event id. To add an endpoint, see [outgoing webhooks](/features/webhooks). Examples and setup steps stay on [message webhooks](/api-reference/legacy/incoming-message).

> [!NOTE]
>
> Outgoing webhooks are on Pro and Agency, and during the 14-day trial. Bulk Message does not include them.

Times are Unix seconds, not milliseconds. A missing message in the recent window is JSON `null`, not `0`.

## Fields

| Field | JSON type | Which deliveries | When it is empty or missing |
| --- | --- | --- | --- |
| `last_messages` | string | All | Empty string when the window has no text |
| `conversation_paragraph` | string | All | Empty string when the window has no text |
| `phone_number` | string, number, or null | All | A string on an incoming WhatsApp message. A number on an outgoing message and on a combined batch. `null` when the contact has no phone number |
| `recipient_name` | string | All | Empty string when the contact has no name |
| `user_id` | string | All | Always present |
| `last_message_of_user` | string | Incoming, combined, and an outgoing delivery that has a contact message | Omitted entirely on an outgoing delivery whose window has no contact message. Not sent as an empty string in that case |
| `last_message_of_bot` | string | All | Empty string when the window has no business message |
| `message_type` | string | All | Incoming text that came from an ad is `referral`. An image or video from an ad keeps `image` or `video`. Outgoing and combined deliveries use the stored type and are not rewritten to `referral` |
| `user_last_message_time` | number or null | All | `null` when the window has no message from the contact |
| `bot_last_message_time` | number or null | All | `null` when the window has no message from the business |
| `attachment_url` | string | All | Always sent, and empty for now. Whatsable does not put a public media link here |
| `note` | string | All | Empty string when the contact has no note |
| `note_automation` | string | All | Empty string when there is no automation note |
| `labels` | string or array | All | A comma-separated string on incoming and outgoing deliveries. An array of strings on a combined batch. Empty string, or an empty array, when the contact has no labels |
| `incoming_message` | boolean | Your own server, and outgoing | `true` on **Your own server**. `false` on an outgoing delivery. Absent on an incoming **Make, Zapier or n8n** delivery, and absent on a combined batch |
| `is_scheduled` | boolean | Incoming and combined | `false` on an incoming delivery. `true` on a combined batch. Absent on an outgoing delivery |
| `send_by` | string | Outgoing only | `WhatsApp App` for a reply typed in the WhatsApp Business app, `AI` for the AI agent and for a proactive follow-up, `Notifyer` for a reply from your team |
| `was_message_by_human` | boolean | Outgoing only | `false` when the AI agent or a proactive follow-up sent it |
| `scheduled_messages` | string | Combined batch only | The batch as one string: `Message 1: "..."`, then a space, U+2014, a space, then `Message 2: "..."`. An empty batch is the string `not text` |
| `referral` | object | Incoming and combined, only with an ad | Absent when the message is not from a Click-to-WhatsApp ad. See [Click-to-WhatsApp fields](/api-reference/legacy/ctwa-referral-fields) |
| `button_reply` | object | Incoming and combined, only on a tap | Absent unless the contact tapped a button or a list row. Keys: `id`, `title`, `message_id`, `whatsapp_message_id`. Each id is `null` when it is unknown. See [button replies](/api-reference/legacy/button-replies) |
| `channel` | string | All | `whatsapp` for a WhatsApp message |
| `username` | string or null | Only when `channel` is not `whatsapp` | Absent on WhatsApp |
| `business_phone_number_id` | string | Only an endpoint set to all numbers | Absent when the endpoint is bound to one number. Appended after `channel` |
| `business_phone_number` | string or null | Only an endpoint set to all numbers | `null` when that number has no display phone |

`send_by` uses `Notifyer` because existing automations branch on that word. It is the previous product name.

## The four shapes

- **Make, Zapier or n8n, incoming.** One request per message. No `incoming_message` key. `phone_number` is a string. `labels` is a string. `is_scheduled` is `false`.
- **Your own server.** Incoming messages only, one request per message. The same fields, plus `"incoming_message": true`.
- **Outgoing.** `phone_number` is a number. Adds `incoming_message`, `send_by` and `was_message_by_human`. No `is_scheduled`. No `referral` and no `button_reply`.
- **Combined batch.** **Make, Zapier or n8n** only, when **Combine messages** is on. `is_scheduled` is `true`, `scheduled_messages` is the batch, `phone_number` is a number, and `labels` is an array. No `incoming_message`, `send_by`, or `was_message_by_human`.

## Related

- [Outgoing webhooks](/features/webhooks): 
Add an endpoint, check the signature, and see how retries work.

- [Message webhooks](/api-reference/legacy/incoming-message): 
Setup steps and payload examples for the same events.