How to set up Framer forms so no lead gets lost
A practical Framer forms setup: choose where submissions go, name inputs properly, design every state, secure webhooks and test before launch.

A contact form is the part of a marketing site that gets tested the least and matters the most. The layout gets a dozen rounds of review, then the form gets one test submission on launch day, if that. When it fails, nothing looks broken. The page still loads, the button still animates, and the enquiries simply stop arriving.
Framer makes it fast to drop a form onto a page, which is exactly why the setup work gets skipped. This guide covers the decisions that keep submissions flowing: where they go, how inputs are named, what people see after they press submit, and how to test the whole path before a client relies on it.
Decide where submissions should end up first
Before you place a single input, ask who will read a submission and where they already work. Framer can send form data to email, Google Sheets or a custom webhook, and the right answer depends on the person at the other end.
- Email suits a solo founder or a small studio with low volume. The message arrives where they already look.
- Google Sheets suits a team that needs a shared record, status columns or a simple monthly count.
- A webhook suits anything that has to start a process: creating a CRM contact, pinging a sales channel or passing the data to Zapier.
For a form that brings in revenue, we like having a record that doesn't depend on someone's inbox. An email can be archived or filtered by accident. A sheet row or CRM record is much harder to lose.
Name every input as if a developer will read it
Input names look like an internal detail until the data leaves Framer. In a webhook, the JSON keys are the input names, so whatever you type becomes part of the integration. Leftover names like "Input 3" force whoever maps the fields to guess, and renaming them later can break a working automation.
Pick a simple convention and keep it across the whole site:
- Use lowercase names with a clear meaning, such as name, email, company and budget.
- Keep the same name for the same field on every form, so one automation can handle them all.
- Treat a rename after launch as a change to the integration, and test it again.
Ask for less than you think you need
Every extra field is one more reason to leave. Start with what the recipient needs for a useful first reply, which is usually a name, an email address and a free-text message. Then challenge each addition: will someone act differently because of this answer?
Framer offers more than ten input types, including text fields, checkboxes, radio buttons and dropdowns. Use the structure when it saves effort on both sides. A budget dropdown with four ranges is easier to answer than a blank field and easier to sort later. A dropdown with fifteen options is a small form-filling chore, so a short text field would serve better.
A good test for each field: if the visitor left it empty, would you still reply? If yes, make it optional or remove it.
Design the states, not just the default
Most form designs show one state: empty and tidy. Real visitors will also see the form while it's sending, after it fails and after it succeeds. Framer lets you design loading, error and success as variants, so give each one real attention.
Loading
Show that something is happening and make the button look busy. Without this, people press it twice or assume the site has frozen.
Error
Say what happened and what to do next. Keep what the person typed visible where you can, and offer another route, such as an email address, so a failed send doesn't end the conversation.
Success
This is the most neglected state and the most useful one. "Thanks!" tells someone nothing. Tell them what happens next and when: "We reply within two working days. Check your spam folder if you don't hear from us." Only make a promise your client can keep.
Set up webhooks properly
Connecting a webhook only takes a minute. Select the form, click Add… next to Send To in the right sidebar, choose Webhook and enter a URL that starts with https://. Getting it right takes a little longer, and Framer's webhook documentation has the details worth knowing:
- Set a secret. It needs at least 32 characters, and you can't view it again afterwards, so store it in a password manager straight away.
- Verify the signature. Each request carries a Framer-Signature header and a Framer-Webhook-Submission-Id header. Your endpoint should recalculate the signature with your secret and reject anything that doesn't match. Otherwise, anyone who finds the URL can post fake leads into your CRM.
- Return a 2xx status. Framer retries up to five times after a non-2xx response. A slow or faulty endpoint could therefore deliver the same lead more than once, so use the submission ID to spot duplicates.
- Use the final URL. Framer doesn't follow 3xx redirects. An old domain or a missing trailing slash that redirects can stop delivery, even though the address works in a browser.
Make email notifications useful
If email is the destination, a generic notification is easy to overlook. Framer lets you customise the subject line, sender name and body. Use a subject that names the site and the form, such as "New enquiry: studio website". A busy founder can then set up an inbox filter and spot real leads at a glance.
Ask your client to send a test to the actual address they'll use, not yours. Shared inboxes and strict company filters are where notifications tend to go missing, and it's better to find that out before launch.
Don't remove spam protection, but check what it catches
Framer describes built-in spam protection and rate limiting for its forms, so you don't normally need to add a captcha on day one. That's good for conversion, since a puzzle is one more obstacle for a real person.
Spam filtering isn't a reason to stop checking, though. In the first couple of weeks, read the incoming submissions and see what gets through. If junk becomes a real problem, narrow it down at the destination first, for example with a filter in your automation, before adding friction for everyone.
Run this test before launch
A single submission from your own laptop proves very little. Before handing over a site, run through this on the published domain, not the preview:
- Submit each form on the site with realistic data and confirm it reaches every destination.
- Check that each field lands in the right column or CRM property.
- Submit from a phone on mobile data, using the phone's keyboard and autofill.
- Try leaving required fields empty and entering a badly formatted email address.
- Read the success state and the error state as a visitor would.
- Confirm who owns the destination, and hand over the sheet, the automation and the secret.
Repeat steps one and two after any domain change or form rename. Those are the changes most likely to break delivery without anyone noticing. A calendar reminder to send a test submission once a month takes two minutes and catches the rest.
The short version
A Framer form takes minutes to build, and the setup around it is what protects the leads. Choose the destination based on who reads it, name your inputs carefully, design all the states, secure your webhooks and test on the live domain. Add this to your handover checklist, and your clients won't discover a broken form by wondering why the enquiries have stopped.


