FRAMER FORMSWhere every enquiry landsA Framer site can look finished while its contact form sends enquiries to an inbox nobody checks. The form takes minutes to build. The decisions behind it belong to the marketing lead: where each submission lands, who hears about it, how it reaches the CRM, and what catches a lead when a step fails.
Where do Framer form submissions go?
A native Framer form sends each submission to the destinations you add under Send To in the form's settings: email, Google Sheets or a webhook. Forms are built into Framer, so there is no plugin to install.
Framer also has built-in components for HubSpot, Typeform, Formspark, Calendly and Intercom, and an Embed component for other providers. Framer's own form audit checklist treats a form with no destination as a launch blocker, and notes that a configured destination does not prove delivery. We work to the same rule.
How do you get Framer submissions into a CRM?
Send them to a webhook. Native forms have no CRM destination of their own, so the usual route is a webhook into Make, Zapier or n8n that finds the contact by email, then updates or creates it. Framer posts each submission as JSON, with each input's name as the key:
{
"first_name": "Jane",
"email": "jane@example.com",
"enquiry_type": "Sales",
"source_page": "pricing"
}Those names are your field mapping, so agree them first:
- Match each input name to a CRM property, such as
emailorfirst_name, and use the same names on every form. - Give select and radio options the exact values your CRM dropdowns expect.
- Return a 2xx status. Framer retries a failed delivery up to five times and doesn't follow redirects.
- Set a webhook secret of at least 32 characters and check the
Framer-Signatureheader where your tool allows it. - Store the
Framer-Webhook-Submission-Idheader and skip IDs already processed, so a retry never creates a second contact.
When is the CRM's own form the better choice?
When the CRM's visitor tracking matters more than design control. Framer's HubSpot component places a HubSpot form using the portalId and formId from HubSpot's embed dialog, and Framer says it is the only way to send submissions straight into HubSpot. With HubSpot's tracking code on the site, the submission is then linked to the visitor's earlier page views through HubSpot's cookie.
The trade-offs: fields and styling are edited in HubSpot, not Framer, and ad blockers or strict company networks can stop HubSpot's script loading, leaving a blank form. We choose it for campaigns where each lead's journey matters. Our guide to HubSpot forms on Webflow covers the tracking and consent detail, which doesn't depend on the site builder.
Can you record where each lead came from?
Yes, with hidden fields. Add an Input to the form, switch on its Hidden property and give it a name, which then appears in every submission. Don't hide a field with the Visible property instead: Framer leaves invisible inputs out of the submission entirely.
A fixed value per page, such as pricing, shows which form produced each lead when several forms share one webhook or sheet. Hidden fields don't read UTM parameters on their own, though Framer says a code override can pass them in. Its Campaign tracking setting, under Site Settings > Forms, adds the five standard UTM parameters and the Google Ads gclid to native form submissions, but it isn't included on every plan.
Who gets notified, and what catches a failed step?
Every form needs a named owner and three decisions:
- The record: where the lead lives, usually the CRM, or a Google Sheet for a small team.
- The alert: an email to a shared inbox or team channel, so holidays and staff changes don't strand enquiries.
- The safety net: in the automation, write each submission to a sheet before the CRM step, and send errors to someone who will act on them.
Give the form a tracking ID too. Framer's Analytics lists tracked form submissions under Tracking, which gives you a monthly count to compare with new CRM contacts.
How should you handle spam and consent?
Framer forms come with spam protection and rate limiting: Basic protection is on by default, and Advanced adds an AI check on some plans. The choice that matters is filtering. Block stops flagged submissions reaching any destination. Pass delivers them marked: [Spam] or [Possible Spam] in the email subject, a Framer Spam Detected column in Google Sheets, and an X-Framer-Spam-Classification header on webhooks. We use Pass and route flagged leads to a review list, so a real enquiry is never dropped unseen. For extra layers, see stopping contact form spam without a CAPTCHA.
On privacy, Framer's help centre makes the site owner responsible for the personal data its forms collect. Put a short notice by the submit button saying how you will use the details, linked to your privacy policy. Add a consent checkbox only for marketing, unticked by default, and map its true or false value to its own CRM property. Rules vary by country, so check the ones that apply to you.
Where to start
Write down the owner, record, alert and safety net for each form. Then send a real test submission on the published site, before launch and after any form change, and check every destination: the email, the sheet row, the CRM contact and the hidden values. If you would like the forms set up and tested with the rest of the site, start with our Framer websites service.
FAQ
Frequently asked questions
Can Framer send form submissions to Google Sheets without Zapier?
Yes. Google Sheets is one of the native destinations under Send To, alongside email and webhooks, so a simple log needs no automation tool. The name you give each field is what identifies it in the sheet. A sheet is a record rather than an alert, though, so pair it with an email notification to whoever owns the enquiries.
Can a Framer form send leads to a CRM other than HubSpot?
Yes, through a webhook. Native forms send to email, Google Sheets or a webhook, so the CRM receives leads through Make, Zapier, n8n or any endpoint that accepts JSON. Framer's guide for Clay shows the pattern: paste the webhook URL into Send To, publish, submit the form once and check that a new record appears.
How do we know a webhook request really came from Framer?
Set a secret on the webhook destination. It must be at least 32 characters, and Framer shows it only once. Every request then carries a Framer-Signature header, a SHA-256 signature of the form data and submission ID made with your secret. Your endpoint recalculates it and rejects any request that doesn't match. Never put the secret in client-side code.
Can Framer form submissions count as conversions in Google Analytics?
Yes. Give the form a tracking ID and Framer fires a framer:formsubmit browser event each time it is submitted. A short script in the site's Custom Code can listen for that event and pass it to Google Analytics, Segment or a similar tool. Framer's own Analytics also lets you use tracking IDs in Funnels and A/B tests.
Why aren't submissions from our Framer HubSpot form showing up in HubSpot?
Usually the component points at the wrong form. Framer's troubleshooting guide lists a mistyped portalId or formId, a form from another HubSpot account, a staging or duplicated form, and a HubSpot form still in draft. Copy both IDs again from HubSpot's embed dialog, publish, submit a test entry on the live site and check HubSpot's submission log.
What happens if we rename a form field after launch?
The data changes shape. Framer uses each input's name as its key in the webhook data, so renaming phone to phone_number sends a key your automation doesn't expect, and that field stops reaching the CRM. Change the name in the form and in the mapping together, then send a test submission through every destination before you publish.

