How Do You Get Jotform Submissions Into Airtable?
Jotform is good at the part people see: a clean form, conditional questions, uploads, signatures. The trouble usually starts after someone presses Submit. The submission lands in an inbox, and someone on your team copies it into Airtable, finds the right client, and tells the next person it's there.
None of that copying needs a person. This post covers the routes from Jotform into Airtable, how to choose between them, how to design a form so every answer has somewhere to go, and the point where a form should become a portal instead.
Short answer: two routes cover most intake
Jotform's built-in Airtable integration handles the simple case: one form feeding one table. An automation platform such as Make or Zapier handles everything after that, when a submission has to find an existing client, create linked records, or notify the right person. For the rare flow neither covers, Jotform's webhooks and API are there.
Route one: Jotform's built-in Airtable integration
Jotform can send each submission straight to an Airtable table, with each form field mapped to a column. If your intake really is one form into one table, such as a contact form or an event registration, this is the quickest way to stop copying by hand, with no extra tool to maintain.
Its limit is relationships. Real intake rarely stays in one table: a submission belongs to a client who already exists, a job that needs creating, a staff member who should be assigned. Once a submission has to look something up and link to it, you've outgrown the direct connection.
Route two: Make or Zapier, for submissions that land in several places
An automation sits between the form and the base and does what the person used to do. It reads the submission, finds the matching client in Airtable or creates one, creates the record linked to the right people, and sends the notification.
On The Best Notary's portals, a Make scenario creates the Airtable record from each Jotform submission, linked to the right client, notary and employer, and each of them then sees it in their own portal.
The automation is also where the rules live: who gets told, which status a new record starts in, what happens when a lookup finds nothing. Writing those rules down is most of the work.
Design the form around the records
The most common mistake is building the form first and working out where the answers go later. Start from the other end:
- Map every question to a field. If an answer has nowhere to go in the base, ask whether you need it at all.
- Use conditional logic to keep it short. A complex intake can ask only what applies to this person, so a long form feels like a short one.
- Carry IDs, not names. When you send a form to an existing client, prefill a hidden field with their record ID through the form link. Matching on a typed name breaks the first time someone spells it differently.
- Decide what's required. A required field in the form is cheaper than chasing missing information afterwards.
Test every branch before it goes live
Conditional forms fail in the branches nobody tried. Before switching an intake on, send a sample submission down every path and check the record each one creates: the links, the status, who was notified. It takes an hour, and it catches the problems your clients would otherwise find for you.
When a form should become a portal
Jotform with good connections is usually the simpler answer, until people need to find, edit or report on what they submitted. A form is a one-way door. If staff keep asking for a copy of what they sent last week, or a manager can't see every submission for one client in one place, the form has become the bottleneck.
310TUTORS hit exactly that with session reports in Jotform, and moved them into a portal where the people who wrote them can find and update them.
Frequently asked questions
Should we use the built-in integration or Make? If one form feeds one table and nothing needs linking, the built-in integration. If a submission has to find or link existing records, or notify different people depending on the answers, use Make or Zapier.
Can Jotform handle appointment booking? Yes. Jotform has appointment fields, and a booking can create the record, notify the right person and appear in your portal like any other submission.
Can clients see their submissions afterwards? Once submissions live in Airtable, a portal on top can show each client only their own records, which is the usual way to give them that view.
What if we already have dozens of Jotform forms? Start with the one that causes the most copying. The same pattern then extends to the rest, one form at a time.
The short version
Jotform's built-in Airtable integration is right for one form into one table. Make or Zapier take over when a submission has to find, link and notify, which is most real intake. Design the form from the records backwards, test every branch, and move to a portal when people need to work with what they submitted rather than just send it.
Want your intake mapped, from the questions to the records they create? See how we build it on our Jotform development page, or book a free 30-minute call.
.png&w=1920&q=75)




