Framer’s form element is a convenience, and its endpoint is not yours.

What the built-in form does

Framer’s form element is designed for people building a site in Framer: add fields, set an email address, publish. That is a complete feature and it is not extensible in the direction of an arbitrary endpoint. Recognising that early saves an afternoon of looking for the setting.

The embed route

<form action="https://freelyform.com/f/FORM_ID" method="POST">
  <label for="email">Email</label>
  <input id="email" name="email" type="email" autocomplete="email" required>
  <button type="submit">Get early access</button>
</form>

<style>
  form { display: grid; gap: .6rem; font: 15px/1.5 system-ui, sans-serif; }
  input, button { padding: .6rem .7rem; border-radius: 8px; border: 1px solid #d5d0c4; }
  button { background: #16211f; color: #fff; border-color: #16211f; cursor: pointer; }
</style>

The <style> block is scoped inside the embed, so the form gets its own small design without touching the rest of the page. That is the trade: Framer’s styling stops at the embed boundary.

The code component route

A code component renders a real form element through Framer’s component API and can inherit properties from the page, so the form looks native. It also gives you somewhere to put the submit handler when you want an inline result instead of navigation. More control, more setup, and the better answer for a form that has to look like the rest of the design.

One record, not two

Once the action points at the endpoint, Framer’s inbox stops receiving submissions. That is the point, but it means the endpoint’s record list is now the only place to look when someone asks whether their signup went through.