How to get Webflow submissions to WhatsApp

Does Webflow send form submissions to WhatsApp?

No. When someone fills in a Webflow form, Webflow saves the submission to your site's form submissions and emails a notification to the addresses you've set in your site's form settings. There's no built-in option to send that notification anywhere else.

To get submissions onto WhatsApp, you need a tool that learns about each new submission and then sends a WhatsApp message. That tool can watch Webflow from the outside (Zapier, Make or a webhook) or sit on your site and catch the submission in the browser (a script tag).

If all you want is to notice enquiries sooner, the free option is to turn on push notifications for the inbox that gets Webflow's emails. It works, but those alerts sit among everything else in your inbox, which is why many people want enquiries in WhatsApp instead. We cover the wider reasons in how to get website enquiries on WhatsApp.

Which ways are there to get Webflow forms onto WhatsApp?

There are four practical routes, and they differ mostly in how much setting up they take and whether you need a WhatsApp Business account.

Prices for Zapier, Make and WhatsApp's own platform change from time to time, so check their current pricing pages before you commit.

How to send Webflow submissions to WhatsApp with Zapier or Make

Use Webflow's form submission trigger in Zapier or Make, then add a WhatsApp action that sends the fields to your number. The outline is the same in both tools:

1. Create a new Zap or scenario and choose Webflow as the trigger, with the new form submission event.

2. Connect your Webflow account, pick the site and form, and send a test submission so the tool can see the fields.

3. Add a WhatsApp action. In most cases this connects to the WhatsApp Business Platform, either directly or through a provider such as Twilio.

4. Map the form fields (name, phone, message) into the message, and set your own mobile number as the recipient.

5. Switch it on and send a real test from your live site.

The Webflow side is simple. The WhatsApp side takes more work. Sending through Meta's official platform usually means setting up a Meta business account, using a phone number that isn't already on the ordinary WhatsApp app, and getting a message template approved before you can message someone who hasn't messaged you in the last 24 hours. Meta also charges per message on that platform at the time of writing. Our guide to the WhatsApp Business app and API explains the difference.

Also watch your automation plan's task limits. If the Zap or scenario stops because you've run out of tasks, the enquiries still reach Webflow, but nothing tells you on WhatsApp.

How to do it with a Webflow webhook and your own code

If you have a developer, Webflow can post each submission straight to your own server, which then calls the WhatsApp Cloud API. You add the webhook in your site settings under the integrations area and choose the form submission trigger.

Your code receives the submission as JSON, checks it really came from Webflow, picks out the fields and sends a template message through the Cloud API. You avoid an automation subscription and can format the message however you like. In return you look after hosting, error handling, retries and the same template and number rules as above.

Avoid replacing the form's action URL with your own endpoint unless you mean to. A custom action sends the data elsewhere and Webflow no longer stores the submission or emails you about it, so you lose your built-in backup.

How to set it up with a script tag

A form notification service adds one script to your site, catches each submission as the visitor sends it and passes it to WhatsApp for you. Formcrier is one of these, and its Webflow integration works like this:

1. 1

   Add your site

   Sign up and enter your website's address. Submissions are only accepted from the domains you list, so add your webflow.io address too if you want to test there.

2. 2

   Paste the script into Webflow

   Copy your script from Sites → Install. In Webflow, go to Site settings → Custom code → Footer code, paste it in, save and publish.

   HTML Copy

   <script src="https://cdn.formcrier.com/v1/formcrier.js" data-key="pk_live_…" async></script>

3. 3

   Switch on your forms

   Open a page with a form. It appears under Sites → Forms, switched off. Switch on the ones you want alerts for.

4. 4

   Connect WhatsApp

   Go to Alert destinations → Add destination → WhatsApp and scan the QR code. WhatsApp opens with a short message ready. Press send and the dashboard shows Connected.

5. 5

   Send a test enquiry

   Fill in your form as a customer would. The alert should reach your phone within a few seconds.

You don't need a WhatsApp Business account: alerts come from Formcrier's number to the WhatsApp you already use. Webflow's custom code setting needs a paid Webflow site plan at the time of writing.

The script knows Webflow forms, so it waits for Webflow to confirm the submission worked before sending an alert. A form that fails its own checks doesn't alert you. If a form redirects to a thank-you page, the page may move on before Webflow confirms, so the submission is sent anyway and marked "success not confirmed" in your dashboard.

Nothing about your form changes. Webflow still saves the submission and sends its email, and if Formcrier can't be reached, the form carries on as normal. The Free plan includes 10 alerts a month to one destination, and paid plans start with a 14-day trial with no card. The full details are in the script docs and the guide to where alerts go.

Why aren't Webflow WhatsApp alerts arriving?

Most missing alerts come down to an unpublished change, a mismatched domain or a step that has quietly stopped. Work through these in order:

The site wasn't published after adding the code

Webflow only puts custom code live when you publish. Publish to every domain you use, including the custom domain.

You're testing on a domain that isn't allowed

With a script, the page's domain has to be on the allowed list. Add your webflow.io address or subdomain exactly as it appears in the browser.

The form is still switched off

New forms start switched off. Turn the form on, or switch on listening to all forms.

The automation has stopped

Check the Zap or scenario is on, hasn't hit its task limit and hasn't lost its Webflow or WhatsApp connection.

WhatsApp rejected the message

On Meta's platform, a message outside the 24-hour window needs an approved template. Check the template's status and the error in your automation's history.

The spam filter held the test

A form sent within seconds of the page loading, or full of links, can look like a bot. Check your spam folder or list before changing anything else.

For Formcrier, the Overview page shows whether the script has been seen and whether each alert was delivered, with the reason if it wasn't. If WhatsApp can't be reached, the alert is emailed to you instead unless you've switched email fallback off.

If spam is the bigger problem, our guide to stopping contact form spam covers Webflow's own options and others. And if a team chat suits you better than a phone, the same approach works for Webflow submissions to Telegram.