Webflow form delivery: why form notifications go missing, and how to fix it

Visitors submit your Webflow form and you can see the submissions in Webflow. But the notification email does not arrive, arrives late, or lands in spam.

How Webflow sends form notifications

When a visitor submits a Webflow form:

1. Webflow stores the submission, so you can see it in the site’s form submissions.
2. Webflow emails a notification to the recipients set in the site’s form settings. On Starter, Core and Freelancer Workspaces it comes from [email protected]; on Growth Workspaces and above it comes from [email protected].
3. You can set the sender name, the subject and a Reply-To (for example the visitor’s email field), but not the mail server.

Common reasons the email does not show up:

• The recipient address in the form settings is wrong or was never confirmed.
• Your mail provider or a company filter moves messages from no-reply senders to spam.

Check where it breaks

1. Submit your own form with an address you control. Wait a few minutes. Check the inbox and spam folder.
2. Check the submission in Webflow. If it is there, the form works; only the email step fails.
3. Check the notification settings in your site’s form settings: recipients, sender name and Reply-To.
4. Check filters and rules in Gmail or Outlook, and ask your IT team about company filters.

Send submissions through SecureSMTP

1. Sign up at securessmtp.com/signup (the Free plan includes 5,000 emails a month).
2. Dashboard → Sites → + Add website. Copy the API key from the last step. It is shown only once.
3. In Zapier, Make or n8n, start with the Webflow form-submission trigger. Or create a webhook URL in the tool and add it in Webflow under Site settings → Apps & integrations → Webhooks with the trigger Form submission.
4. Add an HTTP POST step (Webhooks by Zapier, Make’s HTTP module or n8n’s HTTP Request node) to https://securessmtp.com/api/v1/mail/send with the header x-securessmtp-api-key: <your key> and a JSON body:

   {
     "to": "[email protected]",
     "subject": "New form submission",
     "text": "<mapped message field>",
     "reply_to": "<mapped email field>",
     "from": { "name": "Your Site" }
   }

5. Submit the form once. The email shows up in the Email log in your SecureSMTP dashboard.

To store the submission in SecureSMTP as well (with the form spam check), POST to /api/v1/forms/submit instead, with form_id, form_name and a fields object. See the Forms API guide.

Frequently asked questions