Get the next one in your inbox.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.
Route a single Webflow contact form's submissions to sales, support, or partnerships based on a dropdown value, using FormBridge's conditional routing — no duplicate forms required.
Get an instant summary, key takeaways, action items, and answers to your questions about this article.
Add a select field like inquiry-type to the Webflow form, point the form at a FormBridge endpoint, and set up conditional routing rules in FormBridge that check the field's value and send matching submissions to a different recipient list per rule — one form, several destinations.
A single Webflow contact form can serve both sales and support if it asks one extra question — usually a select or dropdown for "what's this about?" — and FormBridge routes the resulting submissions based on the answer.
In the Designer, add a Select field to the existing form (or a set of radio buttons) with a clear name, e.g. inquiry-type, and options like:
Sales
Support
Partnerships
No special naming convention is required — FormBridge reads whatever field name you set.
Set the form's Custom Action (in its settings panel) to your endpoint:
https://app.formbridge.ai/api/forms/fb_8h2k9p
In the FormBridge dashboard, open the form and set up conditional routing rules that check the inquiry-type field's value:
inquiry-type equals Sales → notify sales@yourcompany.cominquiry-type equals Support → notify support@yourcompany.cominquiry-type equals Partnerships → notify partnerships@yourcompany.comEach rule can point at its own recipient list, independent of the default notification list, so a submission only reaches the team it's actually for instead of everyone getting every inquiry.
Building three copies of a contact form to fake routing means three sets of styling to keep in sync, three places to update copy, and three separate spam-protection setups. One form with one extra dropdown and a routing rule per value keeps the design, validation, and animations in one place in Webflow, while FormBridge handles the "who sees this" logic entirely from its dashboard — no republish needed to change where an inquiry type routes.
Sales, support, and partnerships each keep their own recipient list (and can layer on their own CC list), but they're all still submissions from the exact same visible form — routing changes where the notification email goes, not how the submission is recorded.
Keep a default recipient (or CC yourself) on submissions where inquiry-type doesn't match a configured rule, so nothing falls through if a field is left blank or a new option gets added to the dropdown before a matching rule exists.
No. One form with an added dropdown field is enough — FormBridge's conditional routing sends the notification to different recipients depending on which option was selected.
It's worth keeping a default recipient or CC on the form's base notification settings so nothing goes unseen if a submission doesn't match a configured rule — for example if a new dropdown option is added before a matching rule exists.
One email when we publish something worth reading. No spam — appropriately enough, we'd know.