Loading…
Productivity · Integration Guide5.0/5.0 on Upwork · Top Rated
Jotform Airtable integration
Jotform to Airtable, wired so submissions become clean records with the right field types instead of everything dumped as text.
Buri IlterEx-Jotform engineering lead · LinkedIn
Airtable is where a lot of teams run their actual operations: a CRM, a project tracker, an inventory list, a content calendar, all in a database that feels like a spreadsheet. Connecting Jotform to it means form submissions become structured records you can filter, link, and automate, instead of rows you have to clean up by hand.
The integration is more capable than Google Sheets but also more particular, because Airtable has real field types. A single select, a linked record, a date, an attachment, and a checkbox each expect data in a specific shape. Map a form field to the wrong type and the record either rejects the value or stores it as plain text that breaks your views and automations. This page covers how the mapping works, the field-type traps, and when a webhook gives you the control the native integration doesn't.
I spent five years on Jotform's product team. Airtable users were some of the most sophisticated, and their tickets were almost always about field types and linked records, not about whether data arrived. Here's how to wire it so records land typed correctly.
How it works
How Jotform and Airtable connect.
- 01
Authorize Airtable and pick a base and table
In Jotform's Integrations tab you authorize Airtable and select the target base, then the specific table within it. Every submission creates a new record in that table. Pick the table deliberately, because records go where you point them with no further routing.
- 02
Map form fields to Airtable fields
You map each form field to a column in the table. Airtable's column type matters: text to a text field, a date field to a date column, a number to a number column. The mapping screen is where you line these up, and getting the types right here prevents most downstream breakage.
- 03
Submissions create typed records
On submit, Jotform creates a record with the mapped values. When the types match, the record is immediately usable in filters, groupings, and Airtable automations. File uploads map to attachment fields as URLs that Airtable fetches into its own storage.
- 04
Selects and links must match existing options
Single-select and multi-select fields, and linked-record fields, expect values that already exist (or that Airtable will create as new options). If the form sends a value that doesn't match an option exactly, you can end up with stray options or a failed link. Keep the form's choices and Airtable's options in sync.
Common workflows
What Jotform plus Airtable is actually good at.
- 01
Lightweight CRM intake
A lead or contact form creates a record in an Airtable CRM base, with status and owner fields ready for the team to work. Airtable's views and filters make this a genuine step up from a flat sheet, as long as the field types are set right.
- 02
Project or request intake
A request form feeds a project tracker, each submission a new task record linked to a client or project via a linked-record field. The linking is the payoff and the part most likely to need careful option matching.
- 03
Content or event submissions
Contributors submit content or event details through a form into an Airtable calendar or pipeline, where editors move records through stages. Date and single-select fields carry the workflow, so they have to be mapped to the right types.
- 04
Inventory or asset logging
A form logs new items into an inventory base with category selects and quantity numbers. Works well for steady, structured logging; the select options on the form and in Airtable need to stay aligned.
What breaks
Edge cases that bite in production.
Risk 01
Field-type mismatches store data as the wrong type
Mapping a form field to an Airtable column of a different type (a date string into a text field, a number into a single line) means filters, sorts, and automations on that column stop working as expected. Match the form field to the Airtable field type during mapping, and verify a test record reads correctly in your views.
Risk 02
Select options drift apart
If the form offers choices that don't exactly match the single-select or multi-select options in Airtable, you either get new stray options created or values that fail to map. Keep the form's choice list and Airtable's options identical, and update both together when one changes.
Risk 03
Linked records need a matching key
Mapping to a linked-record field only links cleanly if the incoming value matches an existing record's primary field. A near-miss creates a new linked record instead of connecting to the right one. Send a value you know matches the link table's primary field, or handle the lookup in a webhook.
Risk 04
Attachments are fetched from a URL
Upload fields arrive as Jotform-hosted URLs that Airtable fetches into its attachment field. If the source URL later expires or is access-restricted, the fetch can fail and you're left with an empty attachment. For critical files, confirm Airtable pulled a copy.
Hit one of these edge cases?
I ran into them for five years on the Jotform product team. Book a free call and I'll tell you exactly how to handle your Airtable setup, or send me the details first.
When not to use
When Jotform plus Airtableisn't the right call.
Skip the native integration if you need conditional logic on the way in (routing to different tables or bases, looking up and linking to the correct existing record, transforming values before they land): a webhook or Zapier gives you that control. Skip it if your data model relies on complex linked-record lookups that depend on a unique key the form doesn't capture. And for very high volume, watch Airtable's per-base record limits, since the integration will happily fill a base past what its plan comfortably handles.
Kits that use this
sales
agency
customer success
Automation kits built on Airtable.
Lead Capture → CRM Kit
Lead capture with scoring, dedup, CRM sync, and Slack alerts on the ones worth interrupting for.
Client Onboarding Kit
The onboarding flow every agency wishes they had before their first client was late with assets
NPS & Customer Feedback Routing Kit
NPS that actually does something: detractors escalate, promoters refer, and leadership gets the monthly read
Frequently asked
Questions I get before setting this up.
How do I connect Jotform to Airtable?
In Jotform's Integrations tab, authorize Airtable, choose the base and table, then map each form field to an Airtable column. Match the column types (text, date, number, single-select) to the form fields so records land typed correctly. Each submission then creates a new record in that table.
Why is my Jotform data wrong or unfilterable in Airtable?
Usually a field-type mismatch: a value mapped into a column of the wrong type (a date into a text field, for example) stores as plain text and breaks filters, sorts, and automations. Re-check the mapping so each form field points at an Airtable column of the matching type, then test one record.
Can Jotform link records in Airtable?
Yes, if you map to a linked-record field and send a value that exactly matches the linked table's primary field. A value that doesn't match creates a new linked record instead of connecting to the right one. For reliable linking on a key the form doesn't capture cleanly, use a webhook to do the lookup.
Should I use the native Airtable integration or a webhook?
Use the native integration for straightforward, one-table intake where field types and select options line up. Use a webhook (or Zapier) when you need to route to different tables, look up and link existing records, or transform values before they land, since the native integration writes to a single table with direct mapping only.
Want this wired up without the reading?
Free 20-minute call. I'll tell you which workflow fits your Airtable setup and what it would take to build, or you can send me the details first.