How to integrate WhatsApp with CRM via webhooks: practical guide

For integrate WhatsApp with a CRM without migrating to the official API, the practical path is the webhook: for each event on WhatsApp Web — new lead in the funnel, card moved from stage, deal won — the extension triggers an HTTP POST to a URL that your CRM receives and transforms into a contact, deal or spreadsheet line. At Zapext, webhooks are part of the Plus plan (R$129/month, no cost per message) and work with RD Station, HubSpot, Pipedrive, Bitrix24 and Google Sheets. Below, the conceptual step-by-step and two complete cases.

Understand the direction of the arrow first and foremost

One webhook is an automatic warning between systems: when something happens in tool A, it sends an HTTP request with the event data to a URL in tool B. No scheduled synchronization, no CSV export, no double typing.

In Zapext webhooks, the arrow points in only one direction: from inside WhatsApp Web to outside. The extension notifies the CRM about what happened during the service; it does not receive commands in return — you, your team or the chatbot configured in the extension itself are still the ones who respond to the message. Events are processed locally, on your computer, and only go out to the URLs you register, via HTTPS. Do you need two-way communication (CRM sending messages on WhatsApp)? Skip to the honesty section at the end.

The events that Zapext sends:

• New contact added to the funnel;
• Tag applied or removed to a contact;
• Conversation moved between Kanban columns;
• Service started, ended or transferred;
• Quick message triggered;
• Reminder or schedule completed.

In the Plus plan, webhooks cover the main funnel and service events. The complete list is on the page Zapext integrations.

The conceptual step-by-step guide (valid for any destination)

The screen details change, but the logic is always the same, in five steps:

1. Choose the event that matters. Start with just one. "New contact in the funnel" and "card moved to Gain" are the two with the highest immediate return.
2. Generate the pickup URL at the destination. Each CRM has its own gateway (details per tool below). The result is always a URL that accepts POST.
3. Register the event pair → URL on Zapext. Inside the extension, you paste the URL and choose which event triggers for it. No code.
4. Test with a real event. Move a test card in Kanban and check if the record appeared in the destination with the right fields (name, phone, stage).
5. Activate and set an owner. Someone on the team checks in the first week whether the data is arriving clean and complete.

How each platform receives the event

This is the part that varies — and that generic tutorials ignore. The summary, verified in official documentation (Jul/2026):

Destiny	Gateway	Do you need an intermediary?
Bitrix24	Native Inbound Webhook (REST)	No
HubSpot	"webhook received" workflow trigger	Depends on plan
RD Station	Conversions API or Zapier	In general, yes
Pipedrive	Zapier or Make	Yes
Google Sheets	Apps Script (doPost) or intermediary	Optional

Bitrix24: the most direct path

Bitrix24 has native input webhooks: in the developer resources area, you generate a URL that calls REST API methods, such as lead creation, according to the official Bitrix24 documentation (Jul/2026). In practice: generate the URL there, paste it into Zapext, and the new WhatsApp lead is born as a lead in Bitrix24 — without a tool in between. One caution: the URL contains the authorization key; treat it as a password.

HubSpot: workflow trigger

The HubSpot knowledge base (Jul/2026) documents the "when a webhook is received" trigger, which enrolls the record in an automation workflow. Two details: the payload needs to be JSON, and the flow depends on a property that identifies the contact — the phone number, in our case. The availability of automation resources varies depending on the contracted plan — confirm before setting up the flow.

RD Station: conversion or intermediary

In RD Station Marketing, the developer documentation (Jul/2026) describes the conversion event via API, which creates or updates contacts in the lead base — and RD maintains official integration with Zapier. The path of least friction for those who don't want to touch the API is the intermediary: Zapier or Make receive the webhook from Zapext and create the conversion in RD, which in turn triggers the automation ruler.

Pipedrive: intermediary

Pipedrive's native webhooks are outbound (from it to other systems); For incoming data, the path documented by Pipedrive support itself (Jul/2026) goes through an intermediary such as Zapier, which receives the event and creates or updates person and business in the funnel.

Google Sheets: the spreadsheet that fills itself in

Two routes: a script in Google Apps Script published as a web app — the doPost function receives the POST and adds the line to the spreadsheet, a standard documented by Google (Jul/2026) — or an intermediary with the "add line" step. The first is free; the second, more comfortable for those who don't want to see code.

Case 1: new lead on WhatsApp becomes a contact in CRM

The most common scenario: the lead calls on WhatsApp, the agent qualifies in the conversation and adds the contact to the extension funnel. At that moment the webhook goes off: the contact is created in RD Station, HubSpot or Bitrix24 with name, telephone number and origin label — without anyone opening the CRM to type.

Why this matters more than it seems: leads answered in the first hour are 7 times more likely to qualify^[1], and 80% of sales require at least five follow-ups^[2]. The lead that enters the CRM in real time also enters the automation ruler — emails, tasks, reminders — while it is still hot. The lead written down "after" in a notebook is the lead that the ruler never reaches.

Case 2: won business becomes a line in the spreadsheet

Second assembly, even simpler: when the card is moved to the "Gain" column of the CRM Kanban, the column change event sends messages to Apps Script, which records the date, contact, and step in the spreadsheet. Result: a closing history that feeds itself, ready for a pivot table, monthly target and salesperson's commission — without anyone needing to "remember to update the spreadsheet" at the end of the day.

The same logic applies to the other side of the funnel: card moved to "Lost" can feed a loss reasons tab — honest raw material for Monday's business meeting.

When Zapext is not the right choice

Three scenarios where the honest answer is "don't install":

• Your team lives inside RD Station CRM. RD itself offers WhatStation, a free Chrome extension that takes their CRM into WhatsApp Web, available from the Free plan, according to the RD Station help center (Jul/2026). If the funnel lives in RD CRM and WhatsApp is just the conversation channel, their native extension solves it at no extra cost. Zapext adds the opposite scenario: the funnel takes place on WhatsApp — Kanban, tags, service distribution — and the corporate CRM is the record that needs to be fed.
• You need two ways. If the requirement is for the CRM to automatically send messages on WhatsApp (transactional notification, billing from the ERP), the path is the official WhatsApp Business API, with approved templates and cost per message. Outbound webhooks don't do this — and be wary of anyone who promises otherwise.
• WhatsApp is a secondary channel. If 90% of your leads arrive via forms and emails, start with your CRM's native automation and come back to this guide when WhatsApp becomes the bottleneck.

Where to start

Choose a single flow — new lead → CRM has the greatest impact —, assemble it, test it with three real contacts and only then add the second. Before integrating, organize your house: a well-structured funnel within WhatsApp is what gives meaning to the events that come out of it, and the CRM on WhatsApp shows how to build this funnel from scratch. Webhooks are part of Zapext's Plus plan (R$129/month, no cost per message, 7-day guarantee) — you can set up your first stream in an afternoon.

Sources

1. [1] The Short Life of Online Sales Leads — Harvard Business Review (2011-03). accessed 2026-05-19.
2. [2] 80% of sales require five follow-ups — Marketing Donut / NSA (2023). accessed 2026-05-19.