Webhook integrationRegister an HTTPS endpoint once. Notifyer POSTs a JSON payload whenever a message is received or sent — including replies typed in the WhatsApp Business app. You do not delete the app.
Point Notifyer at a Make hook, Zapier catch hook, or n8n webhook URL with outgoing enabled. Filter on incoming_message and send_by to react when the owner types on their phone.
Outcome: The same payload as the native nodes, without waiting on a node update.
Your server receives POST JSON, stores direction and send_by, and triggers CRM or AI logic. Agent Skills can create the webhook with --incoming --outgoing.
Outcome: Full conversation capture in your own database, including human phone-app replies.
When send_by is a teammate name, was_message_by_human is true. When send_by is WhatsApp App, the reply was typed on the phone. Automations set was_message_by_human to false.
Outcome: You can see which system and which person sent each outgoing message.
Concrete fields you can map in automation tools or cite in your own docs.
A teammate replies by hand on their phone. Your webhook, n8n, Make, or Zapier trigger still fires. You do not delete the WhatsApp Business app.
TriggerIncoming and outgoing WhatsApp message (outgoing enabled)
| Parameter | Type | Description | Example |
|---|---|---|---|
incoming_message | boolean | false when your business sent the message; true when the contact sent it | false |
send_by | string | WhatsApp App for the phone app; the teammate's name for the Notifyer inbox; the automation name for Make, Zapier, n8n, or API | WhatsApp App |
was_message_by_human | boolean | true when a person sent it (phone app or inbox); false for bots and automations | true |
last_message_of_bot | string | Last message your business sent, whether a human or a bot typed it | Hello n8n |
Same payload as a phone-app reply, except send_by is the logged-in teammate's name instead of WhatsApp App.
TriggerOutgoing WhatsApp message from Notifyer inbox
| Parameter | Type | Description | Example |
|---|---|---|---|
incoming_message | boolean | false — your business sent this message | false |
send_by | string | Logged-in teammate display name from the Notifyer chat inbox | Axel Meta |
was_message_by_human | boolean | true because a person sent it from the inbox | true |
No. Notifyer System supports Meta WhatsApp Coexistence. Keep chatting from the WhatsApp Business app on your phone. Hand-typed replies reach your webhook or Make, Zapier, and n8n trigger with incoming_message: false, send_by: "WhatsApp App", and was_message_by_human: true.
Yes. Enable outgoing events. The JSON payload includes incoming_message (direction), send_by (which system or teammate sent it), and was_message_by_human (person vs bot). Messages typed in the WhatsApp Business app arrive with send_by: "WhatsApp App". Messages sent from the Notifyer chat inbox arrive with the teammate's name in send_by.
No. WhatsAble Bot webhooks are incoming-only (messages to WhatsAble's number). This page is Notifyer System: your own WhatsApp Business number, incoming and outgoing, coexistence included. See the Message webhooks docs for the full JSON.
Unlimited messaging from your own number, team inbox, AI assistant, and automations included.
Pro includes a 7-day free trial · 6-minute setup · Cancel anytime
Whatsable
