You launched a beautifully designed Webflow site for your business. Your contact form looks perfect. Visitors are submitting it. You can see the submissions in Webflow’s dashboard.
But you haven’t received a single email notification. Or you do receive notifications — but they show up in spam, with hours of delay, or sometimes not at all. Inconsistency is the worst kind of email problem, because you can’t trust whether a lead actually came through.
How Webflow handles form notifications
When a visitor submits a form on Webflow:
- The submission is stored in your Webflow project under Project Settings → Forms.
- Webflow sends a notification email through their default Sendgrid relay.
- The “From” address is
noreply@webflow.com(you can’t customize this on most plans). - The “Reply-To” is set to the form submitter’s email so you can reply directly.
This works fine for a couple submissions a week. At higher volume — or with modern Gmail / Outlook filters — three things go wrong:
1. noreply@webflow.com gets spam-filtered
Gmail’s spam algorithm increasingly distrusts messages from automated noreply addresses that aren’t aligned with the destination domain. The Webflow shared sender is a known pattern that gets flagged.
2. Webflow’s default Sendgrid IP pool is shared
When other Webflow sites get reported for spam, the shared IPs can land on blocklists for days. Your perfectly legitimate form notification gets quietly junked because of someone else’s behavior.
3. Reply-to trick triggers DMARC failures
Some recipient servers reject messages where the apparent sender (webflow.com) doesn’t match the reply-to address. This is the same root cause as the Shopify and Squarespace shared-SMTP problems.
The Webflow form-data trap
Diagnose your Webflow delivery problem
Run these checks in order:
- Submit your own form. Use your personal Gmail. Wait 5 minutes. Check inbox AND spam.
- Check Webflow’s form data. Project Settings → Forms. Did the submission appear? If yes, the form is working — only the email step is failing.
- Check notification email settings. Project Settings → Forms → scroll to “Form notifications.” Verify the destination address is correct AND that you’ve added it to the allowlist if Webflow asks.
- Check your domain’s MX records. Use mxtoolbox.com. If the destination domain has no MX record, Gmail / Outlook will silently bounce.
- Send a test from Webflow. Project Settings → Forms → Test → Send test notification. Did it arrive?
If step 2 shows submissions but steps 1 and 5 don’t deliver, you have a delivery problem that needs to be solved outside Webflow.
Three ways to fix Webflow form delivery
Option 1: Add a verified domain to Webflow Logic (Workspace only)
Webflow’s “Logic” feature lets you trigger custom actions on form submit. You can set up Logic to forward the form data to a third-party email service.
Pros: works fully inside Webflow.
Cons: Logic requires Webflow Workspace ($24+/month). Limited send volume per workflow execution.
Option 2: Use Zapier to route form submissions
Webflow → Zapier → Gmail/Outlook. Free for up to 100 submissions/month.
Pros: easy setup, lots of downstream integrations.
Cons: Zapier’s free tier runs Zaps every 15 minutes — that’s a 15-minute delay on every form submission. Above 100/month, $20+/month.
Option 3: Use a webhook integration (recommended)
This is the production-grade fix. Webflow forms support webhooks on all paid plans. You configure the form to POST to an external endpoint, then handle the email delivery there.
Recommended: Webhook setup with SecureSMTP
- Sign up at securessmtp.com/signup — free tier covers 100 submissions/month.
- Dashboard → API keys → Create. Copy the key.
- Webflow Designer → select your form → Settings tab → External submissions → check enabled.
- Paste this as the action URL:
https://api.securessmtp.com/v1/forms/submit - In the same panel, add a custom header:
Authorization: Bearer <your-api-key> - Publish. Submit the form. The notification should arrive in your inbox within 5 seconds.
Why this is better
noreply@webflow.com sender (uses your real domain). Full SPF + DKIM + DMARC alignment. AI spam classifier blocks bot submissions before they reach your inbox. Real-time delivery dashboard. Webhook events you can pipe into Slack, Discord, or your CRM.Webflow native vs webhook delivery
| Feature | Webflow native | Webhook (SecureSMTP) |
|---|---|---|
| Sender address | noreply@webflow.com | yourname@yourdomain.com |
| Delivery latency | 1-30 minutes | < 5 seconds |
| Spam protection | Honeypot only | AI + Turnstile + IP block |
| Delivery dashboard | None | Real-time |
| Bounce handling | Silent | Webhook events |
| Custom auto-reply | No | Yes |
| Fan-out (Slack, CRM) | No | Yes |
Frequently asked questions
Does this work on Webflow Free plan?+
External submission webhooks require Webflow CMS plan or above. If your site is on Free, you have two options: upgrade Webflow to CMS ($14/month), or use the Zapier workaround mentioned in this guide. The webhook route is much faster — Zapier introduces a 15-minute delay between form submission and email delivery.
Will I lose access to Webflow's form data?+
No. Webflow still stores every submission in your project's Forms tab. The webhook adds an email layer on top — it doesn't replace data storage. You can still export submissions, see them in the Webflow dashboard, and access them via Webflow's API.
Can I use multiple destinations (email + Slack + CRM)?+
Yes. SecureSMTP webhooks can fan out to multiple downstream destinations from one form submission. Configure them in your dashboard — common combos are "email to me + Slack notification + push to HubSpot." Each destination is a separate webhook target you configure once.
What about reCAPTCHA / spam protection?+
SecureSMTP includes Cloudflare Turnstile (better UX than reCAPTCHA, no annoying image puzzles), an AI spam classifier, IP-based rate limiting, and per-form abuse detection. All on the free tier. You can still use Webflow's native captcha alongside if you want defense in depth.
Can I send a confirmation to the form submitter?+
Yes. SecureSMTP can fire both a notification to you AND a confirmation auto-reply to the submitter, from the same webhook payload. Useful for "Thanks for signing up, here's what happens next" auto-responses. Configure the auto-reply template in your dashboard.
Will the visitor notice anything different about the form experience?+
No. Webflow's success message still shows after submission. The visitor doesn't see the webhook at all — it's a server-side handoff. The only thing they might notice is that if you set up an auto-reply, it now arrives from your domain instead of noreply@webflow.com, which looks more professional.
How does latency compare to Webflow's native email?+
Webflow's native notification email takes anywhere from 30 seconds to 30 minutes to arrive (variable, depending on their queue and recipient mail server). SecureSMTP webhook delivery is consistently under 5 seconds end-to-end — usually under 2. For high-intent leads, that delivery speed matters.
Ready to fix it?