Create HubSpot contacts from Framer forms. Connect your native Framer forms to HubSpot Connector in 30 seconds with zero client-side API key leaks.
A Framer site is often where a B2B lead first raises a hand, and HubSpot is where marketing and sales take it from there. FramerSend creates a HubSpot contact for each Framer form submission through the CRM v3 contacts API, or updates the existing contact when the email is already known. It recognises the standard inputs, including labels such as "First name", "Phone number" or "E-mail", fills the matching properties (first and last name, phone, company, website, job title, city, state, country and message) and passes every other answer as a property whose internal name matches the field name.
You connect with a private app access token, which FramerSend stores on its server; the published Framer site only knows a public form URL. There is no Zapier step, so a demo request reaches HubSpot within seconds, and when HubSpot refuses one you see HubSpot's reason next to the submission in your FramerSend log, with a Retry button once you have fixed the cause.
What gets created: A HubSpot contact, created with POST /crm/v3/objects/contacts. If HubSpot answers that a contact with this email already exists, FramerSend looks that contact up and updates it with the new answers (PATCH), so a returning visitor never creates a duplicate and never gets lost.
| Framer form field | HubSpot |
|---|---|
| email (also Email, E-mail, work_email, correo…) | emailRequired. Surrounding spaces are removed and common domain typos such as gmail.con or yahoo.con are corrected before the contact is created. |
| name or full_name | firstname and lastnameSplit at the first space: the first word becomes firstname, the rest lastname. First name / first_name and Last name / last_name inputs are used as they are. |
| phone, Phone number, mobile, tel | phoneSent as typed, without reformatting. Not also sent as a custom property. |
| company or organization | company |
| website, jobtitle / job_title / Job Title | website, jobtitleMatched under these names, in any capitalisation. |
| city, state (or province, region), country | city, state, country |
| message, notes, comments, details | messageSent under the internal name message. If your account has no contact property with that name, HubSpot reports it as unknown and FramerSend saves the contact without it. |
| Any other field, e.g. Budget Range | Property budget_rangeLowercased, with anything other than letters, digits and underscores turned into _. Multi-value answers are joined with "; ". If HubSpot says the property does not exist, only that property is left out and the contact is saved with everything else (see Troubleshooting). |
Create a private app in HubSpot
In your HubSpot account settings, open the private apps area under integrations and create an app for FramerSend. Give it the crm.objects.contacts.write scope, which creating contacts needs, and crm.objects.contacts.read, which the Test button uses. Copy the access token it shows; it starts with pat-.
Check the properties your form will fill
List the inputs on your Framer form. Name, email, phone, company, website, job title, city, state, country and message go to HubSpot's matching properties. For every other input, make sure a contact property exists whose internal name is the lowercase, underscore version of the field name, or plan to rename the field in step 4.
Connect HubSpot in the plugin or dashboard
HubSpot is one of the quick picks in the FramerSend plugin inside Framer, and it is also under Dashboard → 2. Connect CRM. Paste the token and click Test. Test reads a single contact with the token, so it proves the token and its read scope without creating anything.
Rename fields to HubSpot internal names
Submit the form once, then open Dashboard → 3. Field Mapping and click Auto-load fields. The HubSpot dropdown offers email, firstname, lastname, phone, company, website, jobtitle, city, state, country and message. Common labels such as "Phone number" or "First name" are recognised without mapping; map anything else that belongs in a standard property, for example "Your role" to jobtitle.
Paste the webhook URL into Framer
In Framer, select the form, open Form → Send to → Add… → Webhook, paste the FramerSend webhook URL (https://www.framersend.com/api/submit/ followed by your form ID) and publish the site. Then send a real submission and look the contact up in HubSpot.
Email is required
Cause: The submission had no field named like an email and no value that looked like an address.
Fix: Add an email input to the Framer form and make it required. Because this is a visitor input problem, FramerSend logs it but does not send you a failure alert email.
Invalid HubSpot Access Token.
Cause: Shown by Test when HubSpot answers 401 or 403: the token was mistyped, the private app was deleted or the token rotated, or the app lacks the contacts read scope.
Fix: Copy the current token from the private app, and check that both contacts scopes are ticked.
HubSpot (HTTP …): …
Cause: HubSpot refused the contact (or the update of an existing one) and its own message follows. Typical reasons: an email address HubSpot considers invalid, a value that does not fit a property's type (text sent to a number or dropdown property), or a token without the contacts write or read scope.
Fix: Open the failed row in Dashboard → 4. Logs, fix the property, scope or field it points to, then click Retry.
The contact was saved, but some answers are missing
Cause: HubSpot said one or more properties do not exist in your account. FramerSend removes only those properties and sends the contact again, so the lead and every other answer are kept. The removed answers are not saved in HubSpot.
Fix: Create the missing properties in HubSpot with matching internal names, or rename the fields in Field Mapping. The complete submission is still visible in Logs.
HubSpot: a contact with … already exists but could not be found to update.
Cause: HubSpot reported a duplicate, but neither its reply nor a search by email returned the existing contact, for example because the token lacks the contacts read scope.
Fix: Add crm.objects.contacts.read to the private app, then click Retry.
One URL instead of a Zap. A typical tutorial chains Framer webhook → Zapier Catch Hook → HubSpot action. With FramerSend the webhook URL is the whole setup, and HubSpot's answer is logged next to each submission.
Custom properties by name. In a Zap you pick each HubSpot property by hand. FramerSend sends every answer under a property name derived from the field name, so a new property in HubSpot plus a matching form field is all it takes.
Create or update in one step. Many automation setups need a separate find step before deciding whether to create or update. FramerSend creates the contact and, when HubSpot reports that the email exists, updates that contact instead.
No task counting. Zapier counts each action as a task against your plan. FramerSend plans have no submission limit, so a busy campaign does not change the bill.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate HubSpot Connector credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to HubSpot Connector properties using our visual dropdown UI.
Paste your webhook URL into your Framer form under Send to → Webhook and publish. Submissions flow automatically.
Every plan includes HubSpot Connector and 100+ other connectors. Pay monthly, yearly, or once. Try it free for 14 days, no card needed.
For one Framer site
For freelancers and small studios
For agencies with many client sites
14-day free trial of every connector, no card needed. Form fields and FramerSend file uploads stay free forever with a free account.
Start freeEncrypted API vault, real-time delivery, and unlimited submissions
Automatically capture and route leads from your Framer forms.
Trigger automated workflows when form submissions arrive.
Keep all your form data in one place, synced in real-time.
Yes. If a contact with the same email exists, HubSpot reports a conflict, and FramerSend finds that contact and updates it with the new answers. Values the form does not send are left as they are.
Yes. Any field that is not one of the standard ones is sent as a property whose name is the field name in lowercase with underscores, for example Budget Range becomes budget_range. Create the property in HubSpot with that internal name first.
HubSpot said those properties do not exist, so FramerSend left out only those and saved the rest. Create the missing properties or rename the fields in Field Mapping.
crm.objects.contacts.write to create and update contacts, and crm.objects.contacts.read to find an existing contact and for the Test button. No other HubSpot scopes are used.
No. It creates a contact. A company answer is stored in the contact's company property, not as a separate company record.
Yes. HubSpot is a quick pick in the FramerSend plugin: paste the token, click Test and the plugin creates the form and shows the webhook URL to paste into Framer.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → HubSpot Connector and add your credentials. They are stored server-side and never exposed in your Framer site, which only gets a public form URL.
Yes, all API credentials are encrypted at rest. The client-side code in Framer only exposes a public Form ID, keeping your private keys entirely secure.
No. FramerSend provides unlimited form submissions across all license tiers so your live website forms never get blocked during high-traffic spikes.