Webflow & Framer Forms: Route Submissions Anywhere

Webflow and Framer both ship native forms, and for a simple contact form on a paid site plan they're genuinely fine. This guide is for the moment they stop being fine — when the spam starts, when you need a file upload without a plan upgrade, when submissions should land in Slack or a spreadsheet instead of a dashboard you forget to check.

The fix doesn't touch your design. A form is just markup that POSTs somewhere; you keep the form you styled and change where it submits — one setting in Webflow, one embed in Framer.

What the native forms give you (credit where due)

Webflow's paid site plans now include unlimited form submissions, with notifications to collaborators and a submissions list in the dashboard. Framer's form component is similarly plug-and-play on its site plans. If you're on a paid plan, receive a handful of legitimate messages a month, and email notifications are all you need — stop reading, the built-ins are enough.

Where they pinch

Five walls people hit, roughly in order of how often we hear them:

1. Spam. "Webflow form spam" is a support-forum genre of its own. The built-in defenses are basic, and the usual advice — bolt on a CAPTCHA — charges your real visitors for the bots' behavior.
2. File uploads are a plan upgrade. Webflow gates form file upload behind its Business site tier. If one client project needs a brief-upload field, that's a steep jump for one input.
3. Routing means Zapier. Getting submissions into Slack, Google Sheets, or a CRM typically adds an automation tool — another subscription, another thing that silently breaks.
4. The free-tier cap. Webflow's free plan allows 50 form submissions — easy to burn before a site even launches properly.
5. Your data lives in the site. Rebuild the site elsewhere (agencies do this constantly) and the submission history doesn't come along.

The pattern: keep the form, swap the destination

A form endpoint is a URL that accepts your form's POST, and both platforms let you point at one.

In Webflow: select the Form element → Form settings → set Action to your endpoint and Method to POST:

Action:  https://shipmyform.com/f/YOUR_FORM_ID
Method:  POST

That's the whole change. Every input keeps its name attribute, which becomes the field name in the submission — your styling, interactions, and success animations stay exactly as designed. Reserved fields work as hidden inputs if you want them (a _redirect to your own thank-you page, a _gotcha honeypot).

In Framer: use an embed/code component containing a plain HTML form, styled with your site's fonts and colors:

<form action="https://shipmyform.com/f/YOUR_FORM_ID" method="POST">
  <input type="text" name="name" placeholder="Name" required />
  <input type="email" name="email" placeholder="Email" required />
  <textarea name="message" placeholder="What can we help with?" required></textarea>
  <button type="submit">Send</button>
</form>

The contact form generator produces this markup with your fields and a matching theme, ready to paste into the embed.

What routes through after the swap

Once submissions flow through the backend, the walls above stop being plan questions:

• Spam dies server-side — honeypot, rate limiting, ML classification, and an LLM review for ambiguous messages, with no CAPTCHA in your visitor's way. Blocked spam doesn't count against your quota.
• Delivery is a toggle, not a Zap — email, Slack, Google Sheets, Notion, webhooks, and 20+ connectors with automatic retries.
• File uploads ride along from ShipMyForm's $5/month plan — no Business tier required on the site builder's side.
• The inbox is portable — searchable, CSV-exportable, and independent of where the site is hosted. Migrate from Webflow to Framer (or anywhere) and the form keeps working by pasting the same endpoint.

The bottom line

You chose Webflow or Framer for the design control. Nothing about form handling requires giving the data side to the same tool — the action attribute is a seam the platforms deliberately leave open. Keep the form you designed, point it at an endpoint, and the submissions become something you route, search, and keep — free for 100 a month, spam defense included.

More context: what a form backend is, or how form-to-email actually works.