How to Use the WhatsApp Group Message Received Webhook
This webhook fires every time a participant sends a message in a WhatsApp group connected to your DoubleTick account. It captures who sent the message, what they said, which group it came from, and when it happened — and sends all of that to a system of your choice in real time.
It fires separately for every message. If ten members send messages in the same group, you receive ten separate webhook events.
Step-by-Step Setup Guide
This webhook activates when a participant sends a message in a WhatsApp group connected to your DoubleTick account.
Step 1: Open Webhooks in DoubleTick
Log in to your DoubleTick account
Go to Settings
Click on Webhooks
Step 2: Create a New Webhook
Click New Webhook
Give it a name — for example: Group Message Monitor
Step 3: Get Your Webhook URL
You need a destination URL — this is where DoubleTick will send the data each time a group message is received.
You can connect it to:
A CRM like Zoho, HubSpot, or Salesforce
An automation tool like Zapier or Pabbly
A spreadsheet like Google Sheets
Your own backend or internal dashboard
For testing, use DoubleTick's Bot Studio to preview the incoming data first:
Open a new tab and go to Bot Studio
Click Create New Bot
Set the trigger to On Webhook
Copy the webhook URL that appears
Step 4: Fill in Webhook Details
Go back to the Webhooks page
Paste the webhook URL
Select your API Number (your WABA/WhatsApp Business number)
Click Continue
Step 5: Choose the Event
Select WhatsApp Group Message Received from the event list
Click Create Webhook
Your webhook is now active.
How to Test It
Add a test number to one of your connected WhatsApp groups
Send a message from that test number in the group
Go to Bot Studio → Capture Response → View Response Data
You will see the message data captured in real time
What Data Do You Receive?
When this webhook fires, it sends the following information to your system:
to
The unique ID of the WhatsApp group where the message was received
from
The phone number of the participant who sent the message
type
The channel type — will always be wa_group for WhatsApp group messages
contact.name
The name of the participant as saved in DoubleTick
message.text
The text content of the message
message.type
The format of the message — TEXT, IMAGE, DOCUMENT, AUDIO, VIDEO, and so on
message.context
Details of the message being replied to — empty if this is not a reply
messageId
The unique WhatsApp ID assigned to this message
receivedAt
The exact date and time the message was received
dtMessageId
DoubleTick's internal unique ID for this message
callbackData
Custom callback data attached to this conversation, if configured — null if not set
isAgentOffline
Whether the assigned agent was offline when this message came in
dtLastMessageId
DoubleTick's internal ID of the last message in this conversation
integrationType
The integration channel — will always be WHATSAPP
lastMessageOrigin
Who sent the last message — CUSTOMER or AGENT
dtPairedTemplateId
ID of the paired template, if the previous message was a template — null if not applicable
dtPairedTemplateName
Name of the paired template, if the previous message was a template — null if not applicable
dtPairedMessageMetadata
Metadata of the paired message — null if not applicable
dtPairedTemplateLanguage
Language of the paired template — null if not applicable
WhatsApp Group Message Received Webhook – Sample Payload
json
Real-Life Business Use Case: An EdTech Company Routing Student Queries from WhatsApp Groups Automatically
The Situation
An EdTech company runs live online courses for working professionals. Each batch of 80 to 120 students has its own WhatsApp group — the primary place where students ask questions, flag issues, and request study materials. With 14 active batches running simultaneously, 14 groups are active at any given time, each with a designated academic coordinator.
The Problem
Coordinators are also managing student records, scheduling sessions, and handling calls. Monitoring 14 groups on top of everything else means messages get missed. A student who posts a question at 11 AM may not get a response until 3 PM — too late if they have a submission deadline that evening.
There is also no way to tell an urgent query from a casual comment. Both sit in the group with no prioritisation. And if a query goes unanswered and the student escalates it later, the support team has no searchable log to look back at.
How the WhatsApp Group Message Received Webhook Solves This
The company connects this webhook to their internal ticketing system.
The moment any student sends a message in any group, it is automatically logged in the ticketing system with the student's name, phone number, group name, and timestamp. The system then scans the message content — anything flagged as an access issue, technical error, or payment query is marked high priority and assigned to the right coordinator instantly.
If the coordinator does not respond within 30 minutes, the ticket escalates automatically to the academic head, who gets a WhatsApp notification with the student's name, message, and how long it has been waiting.
Every message is now on record. If a student complains that their query went unanswered, the team can look it up immediately.
The Result
Every message across all 14 groups is captured and logged automatically — nothing is missed due to group volume or coordinator availability
Urgent queries are routed to the right coordinator immediately, without anyone manually triaging the group
Unanswered queries escalate automatically after 30 minutes
The team has a complete, searchable message history outside of WhatsApp for accountability and review
Summary
The WhatsApp Group Message Received Webhook gives your business real-time visibility into every message sent across your connected WhatsApp groups. Set it up once, and every group message becomes a structured data point your systems can log, route, and act on — without anyone needing to watch the group manually.
Last updated