Framer form submissions: are your notifications reaching the inbox?

Framer is the fastest way we've seen to ship a marketing site. The visual builder is excellent, the CMS is lightweight, and forms work out of the box. But there's a quiet failure mode that hits almost every Framer project after launch: form submissions are captured, the success state fires, and yet no email lands in the owner's inbox. The lead exists in the Framer dashboard — no one sees it for days.

The default Framer notification path

When you add a form to a Framer site and enable "Email notifications", Framer sends a message from an address it controls — typically something like notifications@framer.com or a similar shared sender. From the recipient's perspective this looks like a third-party transactional email, not a message from your brand. That matters for three reasons:

• No custom domain. Your DKIM/SPF/DMARC can't authenticate a message you didn't sign. The recipient's filter sees Framer, not you.
• Shared reputation. You inherit the reputation of every other Framer site's forms. One scammy template on the same sending infrastructure can tank everyone else's placement.
• Promotions tab risk. Even when the mail lands, Gmail tends to file templated notification mail into Promotions. Your team might never scroll that deep.

How to test your Framer notifications

The fastest check is to submit your own form from a few seed inboxes you control. A better check is to submit once and have the notification evaluated across Gmail, Outlook, Yahoo, and Mail.ru seed mailboxes at the same time. That's exactly what Inbox Check is built for.

1. Open your Framer form in a private tab so no session or autofill interferes with the test.
2. Fill the form with a seed address from Inbox Check as the reply-to/email field. Submit.
3. Within 30 seconds you'll see where the notification landed — Inbox, Promotions, Spam, or Not Delivered — with SPF/DKIM/DMARC verdicts.
4. Repeat with a second seed address to make sure the result is stable and not a quirk of one mailbox.

Route submissions through your own sender

If you find Framer notifications consistently miss the primary inbox, the durable fix is to stop relying on Framer's sender altogether. Framer forms can fire a webhook on submission. Route that webhook into Zapier, Make, n8n, or a tiny serverless function and send the notification from an address on your own domain with proper authentication.

Minimal Zapier path

1. In Framer, set the form to POST to a Zapier Catch Hook URL.
2. In Zapier, add a "Send Email" step using a Gmail or custom SMTP account on your real sending domain.
3. Set a descriptive subject ("New lead from framer.example.com — {{name}}") and include all form fields in the body.
4. Publish. Test with a real submission and confirm placement with a seed test.

With this change, the notification now travels over your domain and benefits from your SPF/DKIM/DMARC alignment. Reputation is yours, not a shared pool. And because it's a plain transactional email from your own mail, Gmail tends to file it into Primary.

Authentication basics that move the needle

Once notifications leave over your own domain, the same deliverability fundamentals apply. Get these right and placement becomes boring — the goal we all want.

• SPF — include the SMTP provider you route through (Postmark, SendGrid, Google Workspace, etc.). Single v=spf1 record, no duplicates, no >10 DNS lookups.
• DKIM — publish the provider's public key at the selector they specify. Confirm with a seed test that dkim=pass shows up.
• DMARC — at minimum v=DMARC1; p=none; rua=mailto:dmarc@yourdomain. Monitor aggregates for a month before moving to quarantine.
• Reply-To — set the submitter's email as the Reply-To on the notification so hitting reply in your team inbox goes to the lead, not to a noreply bucket.

Common Framer form deliverability issues

Notifications arrive hours late

Usually an SPF/DKIM mismatch or a greylist at the receiving side. Seed test again after DNS changes propagate (up to 30 minutes) and check whether the Return-Path matches the sending domain.

Landing in Gmail Promotions

Promotions placement is triggered by marketing-looking content: templates with heavy HTML, tracking pixels, marketing-sounding subjects. For a form notification, strip the template. Plain text with one link back to the lead record is almost always Primary.

Outlook marks notifications as junk

Outlook weighs sender history heavily. A brand-new sending domain with zero warm-up will struggle. Route a few notifications to your own inboxes first, mark as Not Junk, and let the reputation build over a couple of weeks.

FAQ