One Form, the Right Inbox: A CMS-Driven Email Router for Webflow
Most contact forms funnel everything to a single inbox. That works until the organization has a second office, a third service line, or one person on vacation — then somebody is sorting and forwarding inquiries by hand, and a lead that should have reached the Baltimore office on Tuesday surfaces on Thursday.
We built the Webflow Form Router to retire that job. It reads each form submission and delivers it to the right recipient, with the right branding, based on rules the marketing team edits themselves.
Built From Pieces You Already Run
The whole system is three pieces: Webflow's own form webhook, an n8n workflow, and Gmail. When a visitor submits a form, Webflow fires the webhook, the workflow normalizes the submission, and the routing decision comes from a table that lives in the Webflow CMS.
The routing table is the design decision that carries the system. Each entry is just a CMS item holding:
- the destination email address
- office branding (logo, colors)
- an optional subject prefix
- an on/off flag
Because the rules are CMS content, changing where inquiries go is a content edit, not a code change. The marketing team opens Webflow and edits an item. Nobody files a ticket.
What Happens to a Submission
- Webflow captures the form and triggers the webhook
- The workflow normalizes the data and compares fields like location, office selection, or service type against the routing table
- The matching route determines the recipient
- The system builds a branded notification for that office: logo, brand colors, a formatted summary of every field, file uploads converted to download links, and a clear action button
- If nothing matches, a designated default recipient catches the submission, so no inquiry is ever lost
A default Webflow form email is a plain-text field dump. The router's version arrives looking like it came from the office it's going to, with the submission laid out for a human to read and act on.
The Same Engine Across a Portfolio
The same n8n workflow can serve several Webflow sites at once, each with its own routing table in its own CMS. That's the shape multi-brand organizations, franchises, and agency rosters need: shared engine, per-site rules. The engine also covers the odder cases as they come up: after-hours routing, escalation for high-priority submissions, load balancing across a team, or one inquiry type fanning out to several recipients.
What Changes for the Team
The person who used to sort the shared inbox stops sorting it. Replies come from the office the prospect actually asked about, hours sooner. And every submission is logged with its routing decision, which turns "did anyone follow up on that?" into a lookup instead of an archaeology project.
Growth is the real test of a routing system, and here it's undramatic: a new office means a new CMS item, and the automation never gets touched.
Contact Interface Multimedia if your contact form has become somebody's part-time job. It's a small build that removes it.
