WebhooksHow-to

Does a WhatsApp Business app reply trigger a webhook?

Yes. A reply you type in the WhatsApp Business app still POSTs to your webhook. You keep the app on the phone. The number stays the same.

Start free trialWebhook integration

Outgoing has to be on for that destination. If it is off, the contact still gets the reply and your webhook never sees it.

How do I turn outgoing on?

Pick where the reply should land: a webhook you built, n8n, Zapier, or Make.

  1. 1Pick where the reply should land: a webhook you built, n8n, Zapier, or Make.
  2. 2Open the WhatsAble dashboard. Go to Developer, add an endpoint, and turn on outgoing. A custom webhook needs outgoing: true.
  3. 3Type a test reply in the WhatsApp Business app. Then check the destination for the POST. If nothing arrives, outgoing is usually still off on that endpoint.

Agent Skill

A phone-app reply only reaches an Agent Skill if that Skill sits on a webhook you created with outgoing enabled. Installing a Skill alone does not deliver the event. https://whatsable.app/vibe-code

What arrives in the payload?

When a phone-app reply hits, three fields line up. incoming_message is false. send_by is "WhatsApp App". was_message_by_human is true.

The same POST also carries the rest of the official message fields. The meanings below match the payload fields page.

Check message_type (text, image, audio, video, document, location). For audio, the transcription appears in the text fields when available.

FieldWhat it is
phone_numberWhatsApp number of the contact in this conversation (digits, often without +). On outgoing events this is the person your business messaged. May arrive as a number or a string.
message_typeThe type of the latest message (text, image, audio, video, document, or location). For audio, the transcription appears in the text fields when available.
last_message_of_userThe last message sent by the user.
last_message_of_botThe last business send, including a human on the phone or in the inbox. Not only a bot.
last_messagesRecent messages in the conversation (about the last 20). On webhook deliveries this is typically a JSON string — parse it before iterating. Each item is typed user (the contact) or bot (the last business send, including a human on the phone or in the inbox). Includes messages from the WhatsApp Business app, the Notifyer inbox, automations, and templates.
last_messages.typeSender type (user or bot). user is the contact. bot is the last business send, including a human on the phone or in the inbox.
last_messages.contentMessage content (empty for media messages). For audio, the transcription appears in the text fields when available.
last_messages.timestampISO 8601 timestamp when the message was sent.
last_messages.content_typeType of content (text, image, audio, video, document, or location).
last_messages.media_urlURL to media file if applicable (valid for 24 hours).
conversation_paragraphHuman-readable summary of the recent conversation.
recipient_nameThe name of the recipient if available.
user_idUnique identifier for the user in your system.
user_last_message_timeUnix timestamp of the user's last message.
bot_last_message_timeUnix timestamp of your system's last message.
attachment_urlURL to media file if the latest message contains media (null for text messages).
noteCustom note field for additional context.
note_automationAutomation-related notes.
labelsComma-separated labels for categorizing the conversation.
incoming_messagetrue when the contact sent this message to your business. false when your business sent it (outgoing). Outgoing events include messages typed in the WhatsApp Business app, sent from the Notifyer chat inbox, or sent by Make, Zapier, n8n, the API, or a bot.
send_byWhich system or person sent an outgoing message. "WhatsApp App" when typed in the WhatsApp Business app; the logged-in teammate's name when sent from the Notifyer chat inbox; the automation or app name for Make, Zapier, n8n, API, or a bot. Empty on incoming messages.
was_message_by_humantrue when a person sent the message (WhatsApp Business app or Notifyer chat inbox). false when a bot or automation sent it.
referralPresent on incoming events from a Click-to-WhatsApp ad or post, and omitted on ordinary chats and most follow-ups. See https://whatsable.app/click-to-whatsapp-ads.

How do I filter for a phone-app reply?

Filter so incoming_message is false, send_by is "WhatsApp App", and was_message_by_human is true.

What can I build with a phone-app reply?

A CRM that knows the owner already answered.

A Sheet log of phone replies.

A downstream automation after a human decision.

Is there proof this works?

Yes. YouTube: https://www.youtube.com/watch?v=njAxHZalMn4

https://www.youtube.com/watch?v=njAxHZalMn4

What this is not

This is not an inbox check, a Click-to-WhatsApp field spec, or a customer JSON dump.

Related

Related

Webhooks

Create the endpoint, enable outgoing, and the reply hits your server as a normal POST.

n8n

The trigger is labelled On new Incoming message event. That string is the node's label, not a filter.

Zapier

Use New Incoming or Outgoing WhatsApp Message.

Make

Incoming & Outgoing Messages under the Notifyer System module.

Vibe Code

A phone-app reply only reaches an Agent Skill if that Skill sits on a webhook you created with outgoing enabled.

Click-to-WhatsApp ads

referral points only to this page. It is present on incoming events from a Click-to-WhatsApp ad or post, and omitted on ordinary chats and most follow-ups.

Sources

Sources

Start Free Trial