A lead taps your WhatsApp button, asks about prices and gives their first name. Your team replies within minutes, and then nothing happens. There’s no email address on file, no budget field filled in and nothing a HubSpot workflow can act on. If you want to sync WhatsApp leads to HubSpot workflows, the chat itself is the problem: it holds the answers as text, where your nurture emails, lead scores and sales tasks can’t reach them.
This guide shows how to get every WhatsApp lead into HubSpot as clean contact data and into the right workflow. It covers where WhatsApp leads come from, why structured answers sync when chats don’t, a step-by-step lead-capture workflow, what works on HubSpot Free and Starter, and how to match, route and measure each lead.
The short answer: collect each lead’s details in a WhatsApp Flow built from a HubSpot form. Flowella sends every completed Flow to HubSpot as a native submission of that form, so form-submission triggers, lead scoring and lists treat it like a website lead. Flowella’s Form Completed and Text Reply triggers cover everything that happens in the chat.
WhatsApp leads reach you in three ways, and each one starts the conversation differently.
| Source | How the chat starts | What reaches HubSpot |
|---|---|---|
| Click-to-chat links and QR codes | The lead taps a WhatsApp link or scans a QR code on your website, emails, signatures or print, then sends a prefilled message. | The first message, in the Last WhatsApp reply message contact property[1]. |
| Click to WhatsApp ads | The lead taps a Facebook or Instagram ad and sends the ad’s prefilled message. | The message, plus Meta’s click ID, the ad ID and the ad’s source URL on the contact[2]. |
| Replies to your templates | You message an opted-in contact first, from a workflow or a bulk send, and they reply, tap a button or open a Flow. | A Text Reply event on the contact timeline, and the reply in Last WhatsApp reply message. |
Every one of these opens Meta’s 24-hour customer service window. When a WhatsApp user messages you, “a 24-hour timer called a customer service window starts”, and while it’s open you can send any message; once it closes, only approved templates[3]. Ads add a bonus: if you reply within that window to someone who came from a Click to WhatsApp ad on Android or iOS, Meta opens a free entry point window that “may remain open for up to 7 days”, during which Meta doesn’t charge for your template or service messages[4].
Tip: give every placement its own prefilled message, such as “Hi, I scanned the spring flyer”, so a workflow can tell sources apart. Our WhatsApp link generator builds these links for you.
HubSpot workflows act on properties: a dropdown value, a date, a lifecycle stage. A chat is a run of messages. “About 10k, probably after Christmas, can someone call me?” is a perfectly good answer for a person and no use at all to a branch that checks whether Budget is “Over £15,000”.
Free text causes three problems in HubSpot:
Structured answers fix all three. A WhatsApp Flow is a form that opens inside the chat, with dropdowns, date pickers, checkboxes and required fields. Meta describes Flows as a way to “book appointments, browse products, collect customer feedback, get new sales leads, or anything else”[3]. When a lead picks an option, the value is exactly the one your HubSpot property expects. For the longer argument, read the real problem with WhatsApp chatbots.
Flowella connects the two halves: the WhatsApp Flow your lead fills in, and the HubSpot form your workflows already understand.
You pick a HubSpot marketing form and Flowella builds the matching WhatsApp Flow, with the same fields, options and required settings. When a lead submits it, Flowella checks the answers against the live form and sends them to HubSpot as a submission of that same form[6]. HubSpot lists it with the page name WhatsApp Flow · form name, and the answers land on the contact’s properties: “same properties, same workflows, same reporting”[7].
Because it’s a real form submission, the rest of HubSpot reacts as it would to a website lead:
For how the form-to-Flow sync works in detail, see From Chat to CRM.
Some moments only happen in the chat, so Flowella logs WhatsApp events on the contact timeline and offers each one as a workflow trigger[9]. Two matter most for leads:
Flowella also adds five workflow actions: Send WhatsApp Template, Send WhatsApp Message, Send WhatsApp Reply, AI Document Reader and Generate Document[10].
| When you want to act on | Use this |
|---|---|
| A form submission from any channel, website or WhatsApp | HubSpot’s own form submission trigger for that form |
| WhatsApp Flow submissions only | Form Completed, filtered on Form Name |
| A new chat from a link, QR code or ad | Text Reply, then branch on Last WhatsApp reply message |
| Waiting for a lead to finish a Flow you sent | HubSpot’s Delay until event step, set to Form Completed |
Flowella keeps two contact properties up to date: Last WhatsApp reply message and Last WhatsApp reply at. It writes them before the Text Reply event fires, so a workflow can branch on the reply straight away. Flowella’s knowledge base explains why that matters:
“HubSpot evaluates event filters such as Text Reply → Message contains against every historical Text Reply event on the contact, not only the newest one. Once a contact has ever sent a matching reply, the filter matches forever.”
So enrol on Text Reply, then branch on Last WhatsApp reply message, with exact matches for fixed choices such as “Book” or “Pricing”.
This workflow qualifies each new lead with four questions, sorts them into tiers and gets the hottest ones to sales within the hour. It follows Flowella’s lead capture and qualification recipe[11]. If this is your first WhatsApp workflow, our step-by-step guide covers the basics.
Would you rather keep your website form to a name and a number? Flowella’s web contact follow-up recipe sends the remaining questions on WhatsApp within minutes of the form, then creates a sales task for leads who are ready to buy.
HubSpot’s workflows tool comes with Professional and Enterprise, so Flowella’s triggers and five actions need those plans. Teams on HubSpot Free or Starter still get most of the lead capture:
| HubSpot subscription | Simple workflows per form | Actions in each |
|---|---|---|
| HubSpot’s free tools | One “Send an email after form submission” workflow | One |
| Starter, Professional or Enterprise without Marketing Hub | One | Three |
| Marketing Hub Starter | One | Up to 10 |
| Marketing Hub Professional or Enterprise | As many as you need | As many as you need |
Source: HubSpot, Automate form submission actions, last updated 28 September 2026[12].
The actions include an internal notification email, creating a task, assigning the contact to a team member (paid users only), adding them to a static list and sending a marketing email. On Starter, a simple workflow can alert a salesperson about each WhatsApp lead and give them a task. What these plans don’t give you is waiting, branching or sending WhatsApp messages from a workflow; you send from Flowella instead[13].
Duplicates creep in when one person reaches you on two channels. Knowing how each system matches records prevents most of them.
“HubSpot automatically deduplicates contacts using email addresses, and companies using domain names.”
Source: HubSpot, Deduplicate records in HubSpot (last updated 2 October 2026)
Phone number isn’t one of the properties HubSpot de-duplicates on[5]. A contact created from a WhatsApp chat starts with a phone number and no email, so if the same person fills in your website form later, HubSpot has no email to match and you can end up with two records for one person.
When a lead submits a Flow, Flowella attaches the answers to a HubSpot contact in this order[6]:
In a Professional workflow, assign the owner inside each tier’s branch. If your sales reps share their own WhatsApp links, put the rep’s name in the prefilled message (“Hi Sam, I’d like to book a call”), enrol on Text Reply and set the owner by branching on Last WhatsApp reply message[1]. On Free or Starter, a form automation can assign the contact instead.
Plain text only reaches a lead inside the 24-hour window. For follow-ups that may run later, use Send WhatsApp Template with a reminder template, or Send WhatsApp Reply, which sends plain text while the window is open and wraps your message in an approved Service template once it has closed[10]. For instant confirmations straight after a form, see whether HubSpot can send a WhatsApp confirmation after a form submission.
If you use HubSpot’s AI Customer Agent, HubSpot’s own Assign to Customer Agent action can hand it a WhatsApp conversation through the Flowella channel in the conversations inbox. That channel needs Sales Hub or Service Hub, Professional or Enterprise, and HubSpot Credits may also be required[15]. The agent replies in plain text and only inside the 24-hour window, so assign it straight after a Text Reply trigger rather than after a two-day delay.
A reply of STOP, UNSUBSCRIBE, CANCEL, END or QUIT opts a contact out of messages from that number, so never label a quick reply button Cancel or Stop. Flowella records opt-outs, not opt-ins, so keep your own record of each lead’s consent[16]. For more automations to run once leads are in, see 9 No-Code WhatsApp Automations for HubSpot Teams.
Flowella writes enough to HubSpot to report on WhatsApp leads next to every other channel[17]:
Speed is worth watching too. Across Flowella, the median first reply time is 3 minutes, and more than 100,000 WhatsApp Flows have been completed[7]. Oaklands College, which uses Flowella for student recruitment, puts the result this way:
“Exceptional engagement platform that transformed our student conversion with 160% increase in same-day applications and 90% WhatsApp response rates.”
Peter Hudson, Director of Admissions, Brand & Customer Innovation, Oaklands College. Read the Oaklands College story
Flowella isn’t the only route, and the right one depends on how your team works.
To weigh them side by side, see how Flowella compares.
WhatsApp leads only help your pipeline when HubSpot can read them. Capture the details in a WhatsApp Flow built from a HubSpot form, let each completed Flow arrive as a form submission, and branch on the properties it writes. Use Text Reply for chats that start without a form, and keep phone numbers and email addresses clean so every answer lands on the right contact.
Flowella works on every HubSpot plan, Free and Starter included, and comes from the team at Discover Digital, a HubSpot Platinum Partner. Start a 14-day free trial with no card needed, see how the HubSpot integration works, or book a demo.
Yes. With Flowella connected, Text Reply enrols a contact when they message you, tap a button or submit a Flow, and Form Completed enrols them when they finish a WhatsApp Flow. Both need HubSpot workflows, which come with Professional and Enterprise.
Yes, when Flowella built the Flow from a HubSpot form. Each completed Flow arrives as a submission of that form, listed as WhatsApp Flow · form name, with the answers on contact properties.
Yes. Forms to Flows, the contact timeline, the Last WhatsApp reply properties and the Flowella inbox work on every HubSpot plan, and HubSpot’s form automations can run on each WhatsApp submission. Flowella’s workflow triggers and actions need Professional or Enterprise.
Ask for an email address in the Flow, store WhatsApp numbers in international format such as +447700900123, and send Flows from workflows where you can. HubSpot de-duplicates on email, not phone number.
They can, and then one form-submission workflow covers both channels. You may prefer a WhatsApp-only copy, because every Flowella sync publishes straight away and edits to a shared form also change your website form[6].