Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Seven real limitations of Webflow's native form handling — and how repointing the form's action at a FormBridge endpoint removes each one without touching the design.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Webflow's native forms only notify one address, can't route by field value, send from Webflow's own sender, and offer basic spam filtering and file handling; pointing the form's Custom Action at a FormBridge endpoint instead adds multi-recipient and conditional routing, custom SMTP, layered spam protection, and file uploads without changing the form's design.
A Webflow form element renders a normal HTML <form> under the hood. Select it in the Designer, open the settings panel, and there's a Custom Action field — put a FormBridge endpoint URL there instead of leaving Webflow to handle the submission, and every input's existing name attribute becomes the field name FormBridge receives. The design, animations, and validation stay exactly as built.
Native Webflow forms send a single notification email to one address configured at the site level. Point the action at FormBridge and set a recipient list plus a CC list under Email Settings — as many people as the inquiry needs, not one.
Webflow can't send a sales inquiry one place and a support ticket another from the same form. FormBridge's conditional routing matches a field's value — say, a "department" select — and sends matching submissions to a different recipient list: one form, multiple destinations.
Native form emails arrive from Webflow's own infrastructure, not your domain. FormBridge supports custom SMTP — connect Gmail, Microsoft 365, SES, or any provider, and notifications and autoresponders send as you@yourdomain.com.
Webflow leans mainly on reCAPTCHA. FormBridge scores every submission automatically before it reaches your inbox, and layers on optional CAPTCHA, an authorized-domains allow-list, and a honeypot field — configured per form, no code required.
Webflow supports file uploads with size and storage caps tied to the site's plan. A FormBridge endpoint accepts enctype="multipart/form-data" uploads independent of your Webflow plan, stores them encrypted, and tracks storage against your FormBridge plan instead.
Native Webflow forms don't reply to the submitter at all. FormBridge's autoresponder sends an automatic, template-driven confirmation the moment a submission clears spam checks, using the submitter's own email field as the reply-to address.
Webflow keeps limited submission records inside the Designer/CMS panel. FormBridge gives every submission a searchable inbox with status, full field data, a processing log, and CSV export.
Nothing about the form's HTML, styling, or interactions in Webflow changes — the only edit is the Custom Action URL in the form's settings panel. Everything above is configured afterward, entirely in the FormBridge dashboard, per form.
No. The Designer's Custom Action field only changes where the submission is sent — the form's fields, styling, and interactions in Webflow stay exactly as built.
No — once a form's action points elsewhere, Webflow no longer processes that submission, so the record and any notification lives in the new backend's inbox instead of Webflow's own form submissions panel.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.