Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Webflow's native form notifications send from Webflow's own infrastructure. Here's how to route a Webflow form through FormBridge with custom SMTP so emails come from your own domain instead.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Repoint the Webflow form's Custom Action at a FormBridge endpoint, then add your email provider's credentials under Account → SMTP Configurations and assign that SMTP account to the form — notifications and autoresponders then send from your own domain instead of Webflow's.
Submit a native Webflow form and the notification email that lands in your inbox comes from Webflow's own sending infrastructure — not your domain. That's fine for a quick heads-up, but it looks off-brand, can land in spam more easily for recipients who don't recognize the sender, and makes "reply to this email" awkward since replies don't go where you'd expect.
Point the Webflow form at a FormBridge endpoint instead of letting Webflow handle it natively, then configure a custom SMTP connection so FormBridge's outgoing mail — both the internal notification and the submitter's autoresponder — goes out through your own provider.
In the Webflow Designer, select the form element, open its settings panel, and set Custom Action to your endpoint:
https://app.formbridge.ai/api/forms/fb_8h2k9p
Field names stay whatever you already set on each input in Webflow — FormBridge doesn't require a special naming convention.
In the FormBridge dashboard, go to Account → SMTP Configurations → + Add SMTP Server and fill in:
smtp.gmail.com, or your provider's host (Microsoft 365, SES, Postmark, etc.)587Click Test SMTP before saving to confirm the connection works.
Each SMTP account can serve one or more forms, but a given form only ever sends through one account at a time — assigning a new one moves it off whatever it used before. One important detail: the form also needs a Notification email set under its own Email Settings, or custom SMTP delivery won't take effect even with the account assigned.
Notification emails to your team, and autoresponder confirmations to the person who filled out the form, both arrive from your domain instead of Webflow's — same Webflow-built form, same fields, no code beyond the one action URL. Branding for each email type (logo, colors, footer) is configured separately, so notifications and autoresponders can look different if you want.
Native Webflow forms are processed and emailed entirely by Webflow's own infrastructure, so the sending address reflects Webflow's mail system rather than the site owner's domain.
No. Only the form's Custom Action URL changes; the SMTP connection and sender identity are configured entirely in the FormBridge dashboard, at the account and form level.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.