Blog

Framer Forms: The Missing Manual

Framer's native form component covers basic contact forms and not much else. Here's how to point it at a FormBridge endpoint for real notification routing and spam control.

← Back to the blog
AI Powered

Explore this article with AI

Get an instant summary, key takeaways, action items, and answers to your questions about this article.

Choose your AI assistant
ChatGPT Perplexity
Quick answer

Framer's native Form component supports basic fields and a single destination email, with no conditional routing, custom templates, or autoresponder. Building the form as plain HTML inside a Code Embed and posting it to a FormBridge endpoint adds notification routing, branded templates, autoresponders, and spam protection.

What Framer's native form actually does

Framer's built-in Form component handles the basics: a handful of input types, a single destination email address, and a plain confirmation message. That's enough for a simple "get in touch" box, but it runs out of road quickly — there's no conditional routing (sending sales questions to one inbox and support questions to another), no branded notification templates, and no autoresponder back to the person who submitted.

Point it at a FormBridge endpoint instead

Framer forms post to Framer's own backend, so to get real control you build the form as a plain HTML form — inside a Code Embed — and set its action to a FormBridge endpoint:

<form action="https://app.formbridge.ai/api/forms/fb_8h2k9p" method="POST">
  <input name="name" placeholder="Name" />
  <input name="email" type="email" placeholder="Email" />
  <select name="topic">
    <option value="sales">Sales</option>
    <option value="support">Support</option>
  </select>
  <textarea name="message" placeholder="How can we help?"></textarea>
  <button type="submit">Send message</button>
</form>

Field names can be anything descriptive — FormBridge doesn't require a prefix or a pre-registered schema, so topic and message work exactly like name and email.

Why this is worth the swap

Getting set up

Create a form endpoint, embed the HTML form above in place of Framer's Form component, and configure notifications, autoresponder, and spam protection from the form's settings. Submissions, including their processing log, show up in your inbox as soon as the first one comes in.

Frequently asked

Does Framer's form support sending to different people based on the answer?

No, the native component sends every submission to one fixed address. Posting to a FormBridge endpoint instead lets you configure a recipient list and CC list, and inspect field values like a selected topic directly in your inbox.

Can I still use Framer's design tools to style the form?

The form itself lives inside a Code Embed as raw HTML, so Framer's visual design panel won't reach inside it — you style it with CSS you write directly, though you can reuse existing class names and colors from your site.

Key facts

  • FormBridge accepts any input field name — there is no required prefix or pre-registered schema.
  • FormBridge lets you set a recipient list, CC list, and a subject line using the {{FormName}} merge tag for notification emails.
  • An autoresponder can reply automatically to the person who submitted, using merge tags built from the form's own field names.

Get the next one in your inbox.

One email when we publish something worth reading. No spam — appropriately enough, we'd know.