How do I connect Typeform to WhatsApp?
Close the gap between Typeform submit and first human touch — webhook-triggered WhatsApp messages, qualification bots, and Zoho/HubSpot sync without copy-paste between tools. Add a Typeform webhook pointing to Ominiflow, map fields to template variables, validate E.164 phone and opt-in, then trigger templates on submit.
Last updated: 24 June 2026
Quick answer: Typeform captures structured responses; Ominiflow receives the webhook payload and sends WhatsApp Utility or Marketing templates, starts a qualification bot, or logs the lead to Zoho/HubSpot — typically within 30 seconds of form submit. B2B teams that respond in under five minutes convert 3–5× more inbound demo requests than those who wait until the next business day.
Common Typeform → WhatsApp flows
- Lead magnet delivery — form submit → PDF or resource link on WhatsApp within 30 seconds
- Event registration — confirm slot, calendar file, venue map, and T-24h reminder sequence
- Support intake — ticket ID, category, and expected response time in Utility template
- NPS / survey follow-up — thank respondent; route detractors (score ≤6) to agent inbox
- B2B qualification — bot asks budget, timeline, and authority after form pre-fill
- Waitlist signup — position in queue and next steps without email delay
Webhook setup (step by step)
- In Typeform Connect → Webhooks, add your Ominiflow inbound URL
- Copy the form ID — use it as a routing key in your automation rule
- Map form fields to template variables: name, email, phone, custom answers
- Validate phone is E.164 (+91XXXXXXXXXX) and opted in before any send
- Choose template category: Utility for confirmations, Marketing for promos (opt-in required)
- Enable CRM sync — create or update Zoho/HubSpot contact with UTM and form answers
Field mapping reference
| Typeform field | Ominiflow use | Notes |
|---|---|---|
| Phone number | Send target, CRM key | Required; validate E.164 |
| Hidden UTM fields | Attribution tags | Pass utm_source, utm_campaign |
| Multiple choice answers | Bot branch triggers | e.g. "Enterprise" → senior AE queue |
| Form ID | Automation router | One webhook URL, many forms |
Direct webhook vs Zapier
| Approach | Pros | Cons |
|---|---|---|
| Ominiflow native webhook | Lower latency (<5s), no per-task cost | One-time field mapping |
| Zapier middleware | Familiar UI, quick prototype | Extra cost, delays, brittle at scale |
Opt-in and template compliance
Add an explicit checkbox: "I agree to receive updates on WhatsApp at the number provided." Log consent timestamp in CRM. Post-submit Utility confirmations are fine; cold promos to scraped numbers are not.
Also see: Zapier + WhatsApp · Lead qualification bots · Platform comparisons · Pricing
FAQ
Can Typeform send WhatsApp without coding? expand_more
Yes — Typeform webhook → Ominiflow automation rule → template or bot. No custom server required for standard flows.
What if the form has no phone field? expand_more
Add a required phone field with country code selector, or run a separate email-to-WhatsApp opt-in flow.
Can one webhook handle multiple Typeform forms? expand_more
Yes — route by form_id in the JSON payload to different automation rules per form.
