Create records in your Airtable bases from form data. Connect your native Framer forms to Airtable in 30 seconds with zero client-side API key leaks.
Airtable is a common back office for Framer sites: job applications, booking requests, partner sign-ups or a simple lead pipeline with views for each stage. FramerSend creates one record in your table for every submission, sending each form field to the column of the same name with Airtable's typecast option on, so Airtable can convert text answers for number, date or select columns where it can read them.
The connection is strict in a useful way. All fields go in one request, and Airtable refuses the whole record when a field has no column with that name, so the form and the table have to agree. An email or name input under another spelling (email, E-mail, Full name) is retried once as Email or Name; any other unknown field is named in the error. Nothing is lost: the submission is kept in FramerSend's log with the reason, and you can retry it once the column exists. Your personal access token never leaves FramerSend's server.
What gets created: A new record in the table you choose, created with POST /v0/{base ID}/{table} and typecast enabled. Existing records are never matched or updated.
| Framer form field | Airtable |
|---|---|
| Every form field | The column with exactly that nameValues are sent as received, except email answers, which are trimmed and get common domain typos such as gmail.con corrected. |
| email, E-mail, Full name… with no column of that name | Email or NameWhen Airtable says the field does not exist, FramerSend retries once with the field renamed to Email or Name. |
| Name, Email, Message (forms created in the plugin or setup wizard) | name, email, messageThose forms start with a mapping that lowercases these three fields. Name your columns that way or change the mapping. |
| Dropdown and multi-choice answers | Single or multiple selectSent with typecast on, so Airtable tries to match the text to the column's options. Whether new options are accepted depends on the column and your permissions in Airtable. |
| Numbers, dates, yes/no answers | Number, date, checkbox columnsConverted by Airtable where it can read the value. |
| File uploads | Link textThe file is stored first and its URL is sent as text, so give it a URL or long text column rather than an attachment column. |
| Submission time | Not addedAdd a created time column in Airtable to record it. |
Create a personal access token
In Airtable's developer hub, create a personal access token with the data.records:write scope (to create records) and data.records:read (used by the Test button), and add your base to the token's access list.
Find the base and table
The Base ID starts with app and appears in the base URL. For the table you can use its name or its ID starting with tbl. The ID keeps working if someone renames the table; FramerSend encodes the name, so spaces are fine.
Build the columns from your form
Create one column per Framer input, spelled exactly like the field name FramerSend sends, including capitals. Pick the column type you want; typecast handles the conversion.
Connect Airtable in the plugin or dashboard
Search for Airtable in the FramerSend plugin inside Framer, or use Dashboard → 2. Connect CRM. Paste the token, Base ID and table, then click Test. Test reads one record from the table, which confirms the token, base and table but not your column names.
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. Submit once and check that the record appears with every column filled.
Missing Airtable Personal Access Token, Base ID, or Table Name.
Cause: Shown by Test when one of the three fields is empty.
Fix: Fill all three fields on the connection.
Invalid Airtable token, Base ID, or Table Name.
Cause: Shown by Test when Airtable refuses to read the table: the token is wrong or lacks the read scope, the base is not on the token's access list, or the table name or ID does not exist in that base.
Fix: Check each value, add the base to the token and include data.records:read.
Airtable: the table has no field named "…". Add a field with exactly that name in Airtable, or map this form field to an existing column in FramerSend.
Cause: A form field has no column with the same name (after the one Email/Name retry).
Fix: Add the column, or rename the field in Dashboard → 3. Field Mapping, then click Retry on the failed row.
Airtable (HTTP …): …
Cause: Airtable refused the record for another reason and its message follows: usually a token without write access to the base, or a value that cannot go into the column even with typecast, such as text sent to an attachment, formula or lookup column.
Fix: Read the message on the failed row in Dashboard → 4. Logs, fix the token or column type, then click Retry.
The record is created but some columns stay empty
Cause: Those columns have no form field with the same name, or the visitor left the field blank.
Fix: Rename the Framer field or the column so the names match exactly.
Names instead of a mapping screen. In a Zap you pick a form value for every Airtable column. FramerSend sends fields by name, so adding a field means adding a matching column and nothing else.
Stricter about stray fields. A Zap ignores values you did not map. FramerSend sends every field, so one field without a column stops the record; rename or map it once and it is solved.
No task per record. Each Zapier action counts as a task. FramerSend has no submission limit.
When an automation platform fits better. Linking records to other tables, updating an existing record, or turning uploads into real attachments needs extra steps. FramerSend creates the record.
Full comparison: FramerSend vs Zapier
Zero code or third-party plugins required
Authenticate Airtable credentials in the FramerSend dashboard. We encrypt and store them securely.
Map your Framer form fields to Airtable 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 Airtable 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. Each field is sent under its own name, and Airtable rejects the record if a name has no column. Rename either side, or change the name in FramerSend's Field Mapping.
Not as attachments. The upload is stored and its link is sent as text, so use a URL or long text column.
No. Every submission creates a new record.
Either works. The tbl ID survives a table rename, the name is easier to read.
Yes. Email answers are trimmed and common domain typos such as gmail.con are corrected. Other values are stored as the visitor typed them.
Sign up for a FramerSend account (or log in). Go to Connections → Add Connection → Airtable 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.