Message webhooks

Message webhooks POST a JSON payload to your HTTPS endpoint whenever a WhatsApp message is received or sent on your connected number — including messages typed by hand in the WhatsApp Business app.

Meta WhatsApp Coexistence is supported on Notifyer System. You do not need to delete the WhatsApp Business app or stop using the number on your phone. After Embedded Signup, the same number works in the WhatsApp Business app, the Notifyer chat inbox, and automations (Make, Zapier, n8n, API, and webhooks) at the same time.

Configure an endpoint once, then use it from n8n, Make, Zapier, or your own server. This page is the full payload reference.

Overview

Webhooks are HTTP callbacks that Notifyer sends to your server when a message event occurs. They cover:

Incoming messages — a contact writes to your business
Outgoing messages — your business sends a message, including:
- Hand-typed replies in the WhatsApp Business app on a phone
- Messages sent from the Notifyer chat inbox (with the teammate’s name)
- Messages sent by Make, Zapier, n8n, the API, or a bot
Click-to-WhatsApp ads — when the inbound message came from a Facebook, Instagram, or WhatsApp Status ad, a referral object identifies the creative, platform, and click (ctwa_clid)

Use this to trigger automations, sync CRMs, attribute ad leads, and log full conversation history — not only inbound chat.

Webhook Configuration

Managing Endpoints

Access Webhook Settings

Navigate to the Developer section in your dashboard sidebar to manage webhook configurations.

Configure Endpoint

Add a new webhook URL. Enable incoming, outgoing, or both depending on which events your endpoint should receive.

Endpoint Requirements

All webhook endpoints must be publicly accessible via HTTPS and configured to accept POST requests with JSON payloads. HTTP endpoints are not supported in production environments.

Your webhook endpoint must:

Accept HTTP POST requests
Process JSON payloads
Return a 2xx status code within 10 seconds
Implement idempotency handling (see best practices below)

Incoming and outgoing WhatsApp messages

Notifyer delivers both incoming and outgoing messages to your webhook or automation trigger — including messages typed by hand in the WhatsApp Business app on your phone. This is possible because Notifyer supports Meta WhatsApp Coexistence. You keep using WhatsApp Business on your phone; those hand-typed replies still reach an external webhook and can start an automation. They are not limited to the Notifyer web inbox.

Trigger n8n (or any webhook) from WhatsApp messages — including replies typed in the WhatsApp Business app

The payload is the same whether you use n8n, Make, Zapier, or a custom webhook. Watch the walkthrough on YouTube.

Direction, sending system, and team member

Use these three fields to tell what happened and who sent it:

boolean

true when a contact sent a message to your business. false when your business sent a message to the contact (outgoing). Filter on this field to run logic only for one direction.

string

Which system or person sent an outgoing message:

`send_by` value	Meaning
`WhatsApp App`	Typed by hand in the WhatsApp Business app on a phone
A team member’s name (for example `Axel Meta`)	Sent from the Notifyer chat inbox by that logged-in user
An automation or app name (Make, Zapier, n8n, API, bot)	Sent by that integration or bot

Empty or omitted on incoming messages.

boolean

true when a person sent the message (WhatsApp Business app or Notifyer chat inbox). false when a bot or automation sent it. Combine with send_by to see both whether a human sent it and which teammate or system did.

Example payload: message typed on the phone

This is the JSON Notifyer POSTs when someone types a reply in the WhatsApp Business app. incoming_message is false, send_by is "WhatsApp App", and was_message_by_human is true.

{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}

last_message_of_bot is the last message your business sent — whether a human typed it in the WhatsApp Business app or the Notifyer inbox, or a bot/automation sent it. last_messages is a JSON string of the last ~20 messages (parse it before iterating). phone_number may arrive as a number rather than a string.

When the same person sends from the Notifyer chat inbox instead of the phone app, the payload is identical except:

{
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}

Webhook payload

When a message is received or sent on your connected number, Notifyer sends a POST request to your endpoint with a JSON body.

Sample payloads

{
  "last_messages": [
    {
      "type": "user",
      "content": "Thank you for the quick response. Can you provide more details about your premium service plans?",
      "timestamp": "2025-06-09T22:08:11.990Z",
      "content_type": "text"
    },
    {
      "type": "bot",
      "content": "I'd be happy to help you explore our premium service options. Let me connect you with a specialist who can provide detailed information.",
      "timestamp": "2025-06-09T21:45:30.417Z",
      "content_type": "text"
    }
  ],
  "conversation_paragraph": "User (10:08:11 PM): Thank you for the quick response. Can you provide more details about your premium service plans? ; Bot (9:45:30 PM): I'd be happy to help you explore our premium service options. Let me connect you with a specialist who can provide detailed information.",
  "phone_number": "14155552671",
  "recipient_name": "Sarah Johnson",
  "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
  "last_message_of_user": "Thank you for the quick response. Can you provide more details about your premium service plans?",
  "last_message_of_bot": "I'd be happy to help you explore our premium service options. Let me connect you with a specialist who can provide detailed information.",
  "message_type": "text",
  "user_last_message_time": 1749506891,
  "bot_last_message_time": 1749504330,
  "attachment_url": null,
  "note": "",
  "note_automation": "",
  "labels": "sales, premium-inquiry",
  "incoming_message": true,
  "send_by": "",
  "was_message_by_human": true
}

{
  "last_messages": [
    {
      "type": "user",
      "content": "",
      "timestamp": "2025-06-09T14:05:12.000Z",
      "content_type": "document",
      "media_url": "https://api.insightssystem.com/vault/LSMumRx1/VR-1aHOci6nP28eHWHJH7JauJkc/Ew7R9w../contract_proposal_v2.pdf"
    },
    {
      "type": "bot",
      "content": "Please upload the signed contract document when ready, and I'll process it immediately.",
      "timestamp": "2025-06-09T14:03:20.000Z",
      "content_type": "text"
    }
  ],
  "conversation_paragraph": "User (2:05:12 PM): [Document] ; Bot (2:03:20 PM): Please upload the signed contract document when ready, and I'll process it immediately.",
  "phone_number": "14155552671",
  "recipient_name": "Sarah Johnson",
  "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
  "last_message_of_user": "",
  "last_message_of_bot": "Please upload the signed contract document when ready, and I'll process it immediately.",
  "message_type": "document",
  "user_last_message_time": 1749472312,
  "bot_last_message_time": 1749472200,
  "attachment_url": "https://api.insightssystem.com/vault/LSMumRx1/VR-1aHOci6nP28eHWHJH7JauJkc/Ew7R9w../contract_proposal_v2.pdf",
  "note": "",
  "note_automation": "",
  "labels": "contracts, document-processing",
  "incoming_message": true,
  "send_by": "",
  "was_message_by_human": true
}

{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hello n8n\",\"timestamp\":\"2026-08-15T12:24:47.000Z\",\"content_type\":\"text\"},{\"type\":\"user\",\"content\":\"hi\",\"timestamp\":\"2026-08-12T12:27:42.746Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (12:24:47 PM): Hello n8n ; User (12:27:42 PM): hi",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "hi",
  "last_message_of_bot": "Hello n8n",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786797014,
  "attachment_url": null,
  "note": "email: alex\nName: Alex",
  "note_automation": "email: alex\nName: Alex",
  "labels": "n8n, webhook-test",
  "incoming_message": false,
  "send_by": "WhatsApp App",
  "was_message_by_human": true
}

{
  "last_messages": "[{\"type\":\"bot\",\"content\":\"Hi, I can help with that.\",\"timestamp\":\"2026-08-15T14:02:10.000Z\",\"content_type\":\"text\"}]",
  "conversation_paragraph": "Bot (2:02:10 PM): Hi, I can help with that.",
  "phone_number": 14155552671,
  "recipient_name": "Alex Martinez",
  "user_id": "158c59e1-ea85-4d0b-b70c-65328ba67a8e",
  "last_message_of_user": "Can you help with scheduling?",
  "last_message_of_bot": "Hi, I can help with that.",
  "message_type": "text",
  "user_last_message_time": 1786722580,
  "bot_last_message_time": 1786802530,
  "attachment_url": null,
  "note": "",
  "note_automation": "",
  "labels": "support",
  "incoming_message": false,
  "send_by": "Axel Meta",
  "was_message_by_human": true
}

{
  "last_messages": [
    {
      "type": "user",
      "content": "Quiero información",
      "timestamp": "2026-08-15T18:18:36.000Z",
      "content_type": "text"
    }
  ],
  "conversation_paragraph": "User (6:18:36 PM): Quiero información",
  "phone_number": "50655550100",
  "recipient_name": "Maria Lopez",
  "user_id": "9232fcef-a570-4a2c-b46b-6cab53aec304",
  "last_message_of_user": "Quiero información",
  "last_message_of_bot": "",
  "message_type": "text",
  "user_last_message_time": 1781734716,
  "bot_last_message_time": 0,
  "attachment_url": null,
  "note": "",
  "note_automation": "",
  "labels": "",
  "incoming_message": true,
  "send_by": "",
  "was_message_by_human": true,
  "referral": {
    "source_type": "ad",
    "source_id": "52540693396957",
    "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
    "headline": "Expo Nissan",
    "body": "Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT con condiciones que juegan a tu favor.",
    "media_type": "image",
    "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
    "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
  }
}

Payload Fields

string | array

required

Recent messages in the conversation (about the last 20). On webhook deliveries this is typically a JSON string — parse it before iterating. Each item includes type (user or bot), content, timestamp, and content_type. Includes messages from the WhatsApp Business app, the Notifyer inbox, automations, and templates.

Show last_messages array

string

required

Sender type (“user” or “bot”)

string

Message content (empty for media messages)

string

required

ISO 8601 timestamp when the message was sent

string

required

Type of content (text, image, audio, video, document, location)

string

URL to media file if applicable (valid for 24 hours)

string

required

Human-readable summary of the recent conversation

string | number

required

WhatsApp 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.

string

The name of the recipient if available

string

required

Unique identifier for the user in your system

string

The last message sent by the user

string

The last message your business sent — whether a human typed it in the WhatsApp Business app or Notifyer inbox, or a bot/automation sent it

string

required

The type of the latest message (text, image, audio, video, document, location)

integer

required

Unix timestamp of the user’s last message

integer

required

Unix timestamp of your system’s last message

string

URL to media file if the latest message contains media (null for text messages)

string

Custom note field for additional context

string

Automation-related notes

string

Comma-separated labels for categorizing the conversation

boolean

required

true 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.

string

Which 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.

boolean

true when a person sent the message (WhatsApp Business app or Notifyer chat inbox). false when a bot or automation sent it.

object

Present on incoming events that originated from a Click-to-WhatsApp ad or post. Omitted on ordinary chats and on most follow-up messages after the first ad-attributed inbound. See Click-to-WhatsApp ads.

Show referral object

string

"ad" or "post"

string

Meta ad or post ID

string

URL of the ad or post (platform is in the host)

string

Ad or post headline

string

Ad or post body copy

string

"image" or "video"

string

Image creative URL

string

Video creative URL

string

Video thumbnail URL

string

Click ID for Meta Conversions API attribution

Click-to-WhatsApp ads

When someone taps Send message on a Click-to-WhatsApp ad (Facebook, Instagram, or WhatsApp Status) and writes to your number, Meta attaches a referral object to that inbound message. Notifyer passes it through to your custom webhook and to n8n, Make, and Zapier triggers. Use it to optimize campaigns: see which creative, which platform, and which ad produced the lead, then label the conversation, route it to the right team, or send ctwa_clid to Meta’s Conversions API.

referral is typically present only on the first inbound message after the ad click. Later messages in the same chat usually omit it. Persist ctwa_clid and source_id (keyed on the contact’s phone) as soon as they arrive.

WhatsApp Status ad placements may omit ctwa_clid. Organic posts use source_type: "post" instead of "ad".

What each field is for

Goal	Fields
Group leads by campaign or creative	`source_id`, `headline`
See Facebook vs Instagram vs other	`source_url` (host is `instagram.com`, `facebook.com`, `fb.me`, …)
Show agents the ad the lead saw	`headline`, `body`, `image_url` / `video_url`, `media_type`
Send conversions back to Meta	`ctwa_clid`

Referral object

Look for referral as a top-level field on the Notifyer payload, or at entry[].changes[].value.messages[].referral if the delivery includes the Cloud API envelope.

string

"ad" when the lead tapped an ad. "post" when they came from an organic post.

string

Meta ID of the ad or post. Use this to group and compare creatives.

string

URL of the ad or post the contact tapped. The host tells you the platform (for example Instagram permalink vs Facebook/ad link).

string

Headline shown on the ad or post.

string

Body copy of the ad or post. May include emoji shortcodes such as :fire:.

string

Creative type: "image" or "video".

string

URL of the image creative when media_type is "image". These URLs can expire — copy any asset you need to keep.

string

URL of the video creative when media_type is "video".

string

Thumbnail URL for video creatives.

string

Click-to-WhatsApp click ID. Pass this to Meta Conversions API for Business Messaging (action_source: "business_messaging", messaging_channel: "whatsapp") so purchases and qualified leads attribute back to the ad.

object

Optional. Welcome message configured on the ad, when Meta includes it.

Cloud API envelope example

This is the Meta WhatsApp Business Account shape. The attribution lives on messages[].referral. Contact identifiers in this example are anonymized; the referral fields match a real Instagram Click-to-WhatsApp ad.

{
  "object": "whatsapp_business_account",
  "entry": [
    {
      "id": "1824807628200899",
      "changes": [
        {
          "field": "messages",
          "value": {
            "messaging_product": "whatsapp",
            "metadata": {
              "display_phone_number": "50660039931",
              "phone_number_id": "1070485179471457"
            },
            "contacts": [
              {
                "profile": {
                  "name": "Maria Lopez"
                },
                "wa_id": "50655550100",
                "user_id": "CR.10162597228035267"
              }
            ],
            "messages": [
              {
                "from": "50655550100",
                "id": "wamid.HBgLNTA2NTU1NTAxMDAVAgASGBQzEXAMPLE",
                "timestamp": "1781734716",
                "type": "text",
                "text": {
                  "body": "Quiero información"
                },
                "from_user_id": "CR.10162597228035267",
                "referral": {
                  "source_type": "ad",
                  "source_id": "52540693396957",
                  "source_url": "https://www.instagram.com/p/DZiVBz7gAF9/",
                  "headline": "Expo Nissan",
                  "body": ":soccer::fire: ¡Llegó el momento de hacer la mejor jugada! :fire:Aprovechá la EXPONISSAN y llevate tu nuevo Nissan Kicks Play Sense MT con condiciones que juegan a tu favor:\n\n:car: Precio de fábrica: $23,900\n:moneybag: Ahorro de $3,000\n:package: Entrega inmediata\n:zap: Financiamiento especial disponible\n\n:hourglass_flowing_sand: Promoción por tiempo limitado.\n\nReservá y cotizá a través de nuestro punto de venta digital:\n:point_right: www.nissancr.com/servicios/solicitar-cotizacion.html\nO contactános por WhatsApp:\n:point_right: https://wa.me/50660039931",
                  "media_type": "image",
                  "image_url": "https://scontent.xx.fbcdn.net/v/t45.1600-4/example.jpg",
                  "ctwa_clid": "AfhN-JKvx8HeFTmfB-Tu11zktQRJ-MNdMV1mwvDNxHnpYrGl-jVf3OEFhLva_MP41zYRe5ErUteWFn3v4gkkjzfIEVr9J_u8GAo3-o6DqShykM4Zsl14FcU5MyThsCoQ"
                }
              }
            ]
          }
        }
      ]
    }
  ]
}

In n8n, Make, or Zapier, add a filter or router: only treat the event as ad-attributed when referral exists (or referral.source_type is "ad"). Map referral.headline, referral.source_url, and referral.source_id into your CRM so reporting matches Meta Ads Manager.

Webhook Management API

You can programmatically manage your webhook endpoints using our API.

Create Webhook Endpoint

POST https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create Register a new webhook endpoint to receive incoming message notifications. Send a valid Bearer token (same credential used for the dashboard).

Request Body

string

required

Full HTTPS URL of your endpoint.

boolean

required

Whether the webhook is enabled.

boolean

required

Incoming message trigger on/off. When true, your endpoint receives messages contacts send to your business.

boolean

Outgoing message trigger on/off. When true, your endpoint also receives messages your business sends — including hand-typed replies in the WhatsApp Business app, Notifyer chat inbox messages, and messages sent by Make, Zapier, n8n, the API, or a bot. Set this to true if an automation must react to messages typed on the phone.

boolean

required

Schedule activity trigger on/off. When enabled, your bot can send multiple sequential messages with natural delays between them — useful for simulating human-like conversation flow.

How to enable in the dashboard Navigate to Incoming Webhooks, click the settings icon next to your webhook, then enable Schedule Activity. A dropdown will appear where you can select your preferred delay duration between messages.

How to enable Schedule Activity and set delay duration

Example workflow When a user sends an incoming message, you can respond with a sequence of messages each sent after a specified delay:

{
  "messages": [
    {
      "text": "Great! Let me check available slots for you...",
      "delay": 0
    },
    {
      "text": "I can see openings on Monday and Wednesday.",
      "delay": 2000
    },
    {
      "text": "Which day works better for you?",
      "delay": 3500
    }
  ]
}

Set waiting_duration to the maximum delay window you need. When schedule_activity is false, set waiting_duration to 0.

number

required

How long (in seconds) to wait for schedule activity when schedule_activity is true. Set to 0 when schedule activity is off.Dashboard presets: 15, 30, 60, 1800, 3600, 18000, 36000, 86400, 172800, 259200, 432000, 604800, 1209600, 2592000, 5184000 (15 seconds → 2 months). Prefer these values if mirroring the app UI.

boolean

required

If true, enables request signing. The server returns a signature_secret once in the response — copy and store it immediately, as it will not be shown again.

Webhook signature toggle in the Add Endpoint dialog

curl -X POST \
  https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer YOUR_TOKEN' \
  -d '{
    "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
    "status": true,
    "incoming": true,
    "outgoing": true,
    "schedule_activity": false,
    "waiting_duration": 0,
    "active_signature": false
  }'

const axios = require('axios');

async function createWebhook() {
  try {
    const response = await axios.post(
      'https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create',
      {
        webhooks: "https://your-domain.com/api/webhooks/whatsapp",
        status: true,
        incoming: true,
        outgoing: true,
        schedule_activity: false,
        waiting_duration: 0,
        active_signature: false
      },
      {
        headers: {
          'Content-Type': 'application/json',
          'Authorization': 'Bearer YOUR_TOKEN'
        }
      }
    );
    console.log(response.data);
    return response.data;
  } catch (error) {
    console.error('Error creating webhook:', error);
  }
}

createWebhook();

import requests

url = "https://api.insightssystem.com/api:qh9OQ3OW/webhook/dev/create"

headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer YOUR_TOKEN"
}

data = {
    "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
    "status": True,
    "incoming": True,
    "outgoing": True,
    "schedule_activity": False,
    "waiting_duration": 0,
    "active_signature": False
}

response = requests.post(url, headers=headers, json=data)
print(response.json())

Response

Returns a JSON object for the created webhook row.

number

Webhook ID.

boolean

Whether the webhook is enabled.

boolean

Incoming message trigger.

boolean

Outgoing message trigger. When true, the endpoint receives messages your business sends, including WhatsApp Business app replies.

string

Stored endpoint URL.

number

Unix timestamp in milliseconds.

number

Schedule activity wait time in seconds.

boolean

Schedule activity flag.

string | null

When active_signature was true: a one-time secret string — copy and store it immediately, it will not be retrievable again. When active_signature was false: null.

{
  "id": 1205,
  "status": true,
  "incoming": true,
  "outgoing": true,
  "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
  "created_at": 1775471874139,
  "signature_secret": "<one-time secret — copy immediately>",
  "waiting_duration": 0,
  "schedule_activity": false
}

{
  "id": 1205,
  "status": true,
  "incoming": true,
  "outgoing": true,
  "webhooks": "https://your-domain.com/api/webhooks/whatsapp",
  "created_at": 1775471874139,
  "signature_secret": null,
  "waiting_duration": 0,
  "schedule_activity": false
}

When active_signature is true, the signature_secret is returned only once at creation time. Store it securely — it cannot be retrieved again. Use it to verify the authenticity of incoming webhook requests.

Webhook Signature Verification

When a webhook is created with active_signature: true, every request our system sends to your endpoint will include an X-Webhook-Signature header. Use it to confirm the request genuinely came from us and was not tampered with.

Header	Example value
`X-Webhook-Signature`	`RNEefV2V_tiDZeiOpeqMzWsR3X4zGOxIYARIF5-Ia2MXWIgT48jO-M4A1-bgr9bxdoHy5vb7azy_Vd-Gsp4qoAVhQCVyWZxhD1ZNJTQi9VNezJ6C7mnPy--osqcDSq1bfjjppAXBlyenWIa8_506ez5Z92p-eGucalu3-1g6wOk`

The value is derived from the signature_secret returned at creation time. Compare it in your endpoint handler to validate each incoming request.

If active_signature was false when the webhook was created, this header will not be present in requests sent to your endpoint.

Never log or expose your signature_secret in client-side code or public repositories. If it is compromised, delete the webhook and create a new one with a fresh secret.

Troubleshooting

Webhook Not Receiving Events

Verify your endpoint is publicly accessible
Check for HTTP 4xx or 5xx responses
Ensure proper SSL certificate configuration
Verify your webhook is enabled in the dashboard
Confirm outgoing is enabled if you expect events for messages you send (including the WhatsApp Business app)

No referral / Click-to-WhatsApp fields on the payload

referral is usually only on the first inbound message after the ad click. Store ctwa_clid and source_id immediately.
Organic messages (not from an ad or post) have no referral object.
WhatsApp Status ad placements may omit ctwa_clid even when other referral fields are present.
Confirm you are looking at referral (Notifyer payload) or messages[].referral (Cloud API envelope), not a Facebook Lead Ad form submission — that is a different Meta product.

"Same webhook exist" error when creating a webhook

Each endpoint URL must be unique. If you submit a webhooks URL that is already registered, the API will return a “Same webhook exist” error.To resolve this:

Check your existing webhooks in the Developer → Incoming Webhooks tab of the dashboard to confirm whether the URL is already registered.
If you want to update settings on an existing webhook (e.g. toggle incoming, change waiting_duration), use the update/edit endpoint instead of re-creating it.
If you genuinely need a fresh webhook at the same URL, delete the existing one first, then create a new one.

FAQs

Do webhooks include Click-to-WhatsApp ad details?

Yes. When the contact’s message comes from a Click-to-WhatsApp ad, the payload includes a referral object (source_id, source_url, source_type, headline, body, media_type, creative URLs, and ctwa_clid). Use it to see which creative and platform produced the lead. Full reference: Click-to-WhatsApp ads.

Do webhooks include messages typed in the WhatsApp Business app?

Yes. With Meta WhatsApp Coexistence you keep the WhatsApp Business app on your phone. Enable the outgoing trigger. Those messages arrive with incoming_message: false, send_by: "WhatsApp App", and was_message_by_human: true. They are POSTed to your webhook — they are not limited to the Notifyer web UI.

How do I tell which teammate sent an outgoing message?

Read send_by. When the message was sent from the Notifyer chat inbox, send_by is that user’s name (for example "Axel Meta"). When it was typed in the WhatsApp Business app, send_by is "WhatsApp App". was_message_by_human is true in both human cases.

How do I handle different message types?

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

Do I need to respond to every webhook request?

Yes. Return a 2xx HTTP status code for every request so Notifyer does not retry unnecessarily.

How can I test webhook delivery?

Use the Test Webhook feature in the Developer section of your dashboard, or send a message from the WhatsApp Business app after enabling outgoing events.

Need assistance?

Our technical support team is available to assist with webhook configuration, payload handling, and integration questions.

Get Started

Whatsable (formerly Notifyer System)

WhatsApp Cloud API errors

Overview

Webhook Configuration

Managing Endpoints

Endpoint Requirements

Incoming and outgoing WhatsApp messages

Direction, sending system, and team member

Example payload: message typed on the phone

Webhook payload

Sample payloads

Payload Fields

Click-to-WhatsApp ads

What each field is for

Referral object

Cloud API envelope example

Webhook Management API

Create Webhook Endpoint

Request Body

Response

Webhook Signature Verification

Troubleshooting

FAQs

Need assistance?

​Overview

​Webhook Configuration

​Managing Endpoints

​Endpoint Requirements

​Incoming and outgoing WhatsApp messages

​Direction, sending system, and team member

​Example payload: message typed on the phone

​Webhook payload

​Sample payloads

​Payload Fields

​Click-to-WhatsApp ads

​What each field is for

​Referral object

​Cloud API envelope example

​Webhook Management API

​Create Webhook Endpoint

​Request Body

​Response

​Webhook Signature Verification

​Troubleshooting

​FAQs

Need assistance?

Overview

Webhook Configuration

Managing Endpoints

Endpoint Requirements

Incoming and outgoing WhatsApp messages

Direction, sending system, and team member

Example payload: message typed on the phone

Webhook payload

Sample payloads

Payload Fields

Click-to-WhatsApp ads

What each field is for

Referral object

Cloud API envelope example

Webhook Management API

Create Webhook Endpoint

Request Body

Response

Webhook Signature Verification

Troubleshooting

FAQs