WhatsApp Group Participant Removed Webhook in DoubleTick
Automatically Track Every Participant Removal and Keep Your Systems Accurate in Real Time
Your team removes a participant from a WhatsApp group. Maybe their subscription lapsed. Maybe they violated a community guideline. Maybe they were added by mistake. Whatever the reason, they are now out of the group.
But your CRM still shows them as an active group member. Your billing system has not been updated. Your access control list still includes them. And no record of the removal exists anywhere outside of the group itself.
These gaps create real problems — from access control failures to inaccurate customer records to compliance issues. The WhatsApp Group Participant Removed Webhook closes them all. The moment any participant is removed from a WhatsApp group through DoubleTick, this webhook fires and sends the removal details to your connected system instantly.
This article will walk you through:
What this webhook is
When it gets triggered
How to set it up step by step
What data you receive
A real-life business example of how it can be used
No technical background needed.
What Is the WhatsApp Group Participant Removed Webhook?
In DoubleTick, a business or group admin can remove a participant from a WhatsApp group at any time. The WhatsApp Group Participant Removed webhook fires the moment this removal happens — capturing the removed participant's details, the group they were removed from, and the exact time of removal.
This is distinct from the Group Participant Left webhook, which tracks voluntary exits. This webhook tracks removals — actions taken by the business, not by the participant. The distinction matters because removals are deliberate, controlled actions that typically require corresponding updates in other systems.
Think of it like a security system that logs every access revocation. The moment someone's access is removed, the system records it — who was removed, from where, and when — so every connected platform can update itself accordingly.
When Does This Webhook Trigger?
This webhook activates when:
A participant is removed from a WhatsApp group by the business or a group admin through DoubleTick
It does not fire when a participant leaves voluntarily — that is covered by the Group Participant Left webhook.
Step-by-Step Setup Guide
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 clear name — for example:
Group Participant Removal Log
Step 3: Get Your Webhook URL
You need a destination URL — this is where DoubleTick will send the removal data the moment a participant is removed.
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 access management system
For testing purposes, you can use DoubleTick's Bot Studio to capture and preview the 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 Participant Removed from the event list
Click Create Webhook
Your webhook is now live and logging every removal the moment it happens.
How to Test It
Add a test participant to any WhatsApp group through DoubleTick
Remove that participant from the group
Go to Bot Studio → Capture Response → View Response Data
You will see all the removal details captured at the exact moment the participant was removed.
What Data Do You Receive?
When this webhook fires, it sends the following information to your system:
Group ID
The custom ID of the group the participant was removed from
Group Name
The name of the WhatsApp group
Customer Phone
The phone number of the participant who was removed
Participant Removed At
The exact date and time the participant was removed
Real-Life Business Use Case
A Paid Investment Research Community Automating Access Revocation When Subscriptions Expire
The Situation
A financial research firm runs a premium investment research community on WhatsApp. Subscribers pay a monthly or annual fee to access exclusive stock analysis, sector reports, portfolio recommendations, and real-time market alerts — all delivered through a set of private WhatsApp groups organised by investment category: large cap stocks, small cap opportunities, macroeconomic updates, and derivatives trading.
Access to these groups is the core product. Subscribers pay specifically for the insights shared in them. The firm has over 800 active subscribers across multiple groups at any given time, with dozens of new subscriptions and renewals happening every week — alongside an equal number of cancellations and lapses.
The Problem
When a subscriber's payment lapsed or they cancelled their subscription, the operations team was supposed to manually remove them from all the WhatsApp groups they had access to. This was a multi-step, manual process — identifying which groups the subscriber was in, removing them from each one, and then updating the CRM to reflect their access revocation.
In practice, this process was slow and error-prone. Subscribers who had cancelled or lapsed were routinely remaining in the groups for days — sometimes weeks — after their subscription had ended, continuing to receive premium research content they were no longer paying for. This was a direct revenue leak.
On the other side, when a removal did happen, there was no automatic record of it anywhere. The CRM was updated manually and inconsistently. If a former subscriber called support claiming they had been removed by mistake, there was no clean audit trail to verify when the removal happened and whether it was correct.
The firm also had no visibility into removal patterns — they could not tell whether certain subscription tiers were churning faster, whether removals were clustering around a particular time of month, or whether there were subscribers who had been removed and never re-subscribed who might be worth targeting with a win-back campaign.
How the WhatsApp Group Participant Removed Webhook Solves This
The firm connects this webhook directly to their CRM via their backend system.
When a subscriber's payment lapses or they cancel, the operations system triggers the removal from all relevant WhatsApp groups through DoubleTick. As each removal happens, the webhook fires and the subscriber's phone number, the group they were removed from, and the exact removal timestamp are automatically logged in their CRM record.
The CRM update happens in real time — the moment the removal is executed in DoubleTick, the subscriber's access status is updated in the CRM to reflect which groups they have been removed from and when. There is no manual CRM update required from the operations team.
If a subscriber is removed from multiple groups — because they had access to several categories — each removal triggers a separate webhook event, and each is logged individually in the CRM. The subscriber's CRM record ends up with a clean, timestamped history of exactly which group access was revoked at what time.
When a former subscriber calls support asking why they were removed, the support agent opens their CRM record and immediately sees the full removal history — which groups they were removed from, the exact date and time of each removal, and the corresponding subscription status at that time. Disputes are resolved in seconds with complete, accurate data.
The firm also uses the aggregated removal data from the CRM for win-back campaigns. Every quarter, they pull a list of subscribers who were removed more than 30 days ago and have not re-subscribed, and send them a personalised re-engagement WhatsApp message highlighting new research content they have been missing — driving meaningful reactivation from an audience that had already demonstrated willingness to pay.
The Result
Access revocation is logged automatically in the CRM the moment it happens in DoubleTick, with zero manual input from the operations team
Former subscribers are removed promptly and the CRM reflects the change in real time — eliminating the revenue leak of lapsed subscribers accessing paid content
Support disputes about access removal are resolved immediately using the clean, timestamped removal log in the CRM
The firm has a complete audit trail of every removal event — which is particularly valuable in a regulated financial services environment where access control documentation may be required for compliance purposes
Win-back campaigns are informed by accurate, automatically generated removal data — identifying the right former subscribers to target with re-engagement offers at the right time
The operations team is entirely freed from the manual work of logging removals, allowing them to focus on subscriber experience and retention instead
Summary
The WhatsApp Group Participant Removed Webhook closes one of the most overlooked operational gaps in group-based businesses — the absence of an automatic record when access is deliberately revoked. Every removal is captured the moment it happens, every connected system is updated instantly, and your team has a complete, timestamped audit trail of every access change. For businesses where group membership is tied to a paid subscription, a compliance requirement, or a controlled access model, this webhook is not just useful — it is essential.
Set it up once, and every group removal is automatically documented, tracked, and actioned across all your systems.
Last updated