An Airtable form is built straight from an existing table: you create a Form view, Airtable fills it with the fields from that table's first grid view, and every submission becomes a new record in the table. The form view works on all plans, but a cover image, logo, custom submit button, redirect and hiding the branding need a Team, Business or Enterprise Scale plan, as of October 2026.
Here's the catch. Airtable now recommends its newer form builder, and the original form view won't get the newest features. The form builder already has default values and warning messages that the form view doesn't. If you're starting fresh, open a form view and you'll see an Upgrade to new forms button at the top right.
Which Airtable form should you use?
| Form type | Best for, as of October 2026 |
|---|---|
| Form builder | Standalone forms shared with a range of audiences; Airtable's recommended route |
| Form view | The original form, generated from a table; still works, but no newest features |
| Interface form layout page | A form shown only to logged-in users with edit access to that interface |
| Record creation form button | Quick record creation for editors inside an interface workflow |
Forms inside an interface need Interface Editor permissions or higher. To build a form view you need to be an Owner, Creator or Editor; Commenters can only make their own personal views.
How to create an Airtable form view
- Open the table where the data will land, open the view sidebar and, under Create, click Form.
- Give the form a title, choose Collaborative or Personal, then click Create new view. You can't lock it until setup is finished.
- Drag fields to reorder them, hide any you don't need, or drag new ones on from the left. Use + Add a field to this table if the field doesn't exist yet.
- Click each field to rename it for the form, add a subtitle or toggle Required.
- Set what happens after submission at the bottom of the builder.
- Click Share form in the view bar to copy the link, or Preview to open it.
Watch the Required toggle on checkboxes: a required checkbox has to be ticked before the form will submit. If you want to test changes, duplicate the form view rather than editing the live one.
Field rules worth knowing
Single select, multiple select and user fields can show as a dropdown or a list. As a list, single options become radio buttons and multiple ones become checkboxes. Select options are cut to under 70 characters on forms, with an ellipsis after that. You can also limit a select or user field to specific options, so respondents only see the ones you pick.
For linked record fields, Limit record selection to a view restricts choices to the records in a filtered view. If you later change that view's filters, Airtable tells you which form depends on them.
Conditional logic shows or hides fields based on earlier answers. Two rules: the first field can't be conditional, and a required field shouldn't be, because it can block submissions when it stays hidden.
After-submission and access settings
| Setting | Plan, as of October 2026 |
|---|---|
| Custom message after submission | All plans |
| Submit another response button | All plans |
| Email the form's creator after each submission | All plans |
| See who submitted, through a Created by field | All plans |
| Edit the submit button label | Paid plans |
| Let people request a copy of their response | Paid plans |
| Hide Airtable branding | Paid plans |
| Redirect to a URL after submission | Paid plans |
| Restrict by password or email domain | Paid plans |
Redirects have a neat trick: the {record_id} variable sends someone to the record they've just created, if they have access to the base. But a redirect switches off the custom message, the submit another response button and the new blank form after 5 seconds. Response copies come from [email protected], which you can't change, and notification emails go to whichever logged-in user ticked the box. Email domain restriction allows one domain per form, so duplicate the view for another domain, which gives it a new URL.
Cover images are always 240px tall and as wide as the browser window, so Airtable suggests at least 800px by 240px, with 1800px by 480px as a good target. Keep anything important out of the image, as it can get clipped. Stop accepting new responses keeps the link alive for later, unlike disabling the shared link. Embedded forms need popups allowed on your site, because redirects open in a new tab.
What Airtable forms can't do
- Multiple pages or branching paths: native forms are single-page.
- Save and resume: respondents can't save progress and come back later.
- Update an existing record: each submission creates a new one, though linked records plus automations can get close.
- Section headers: the community workaround is a single select field with no options, shown as a list.
- Building on mobile: the mobile apps can't create forms, and respondents use the share link in a browser.
Airtable's own help says a third-party form builder that connects to Airtable is the usual answer if you need any of the first three.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Using the When a form is submitted trigger
- In the base, click + Create automation and choose When a form is submitted.
- Select the table, then Select a form, and pick the standalone form or form view.
- Test the trigger so details like record ID and created time become tokens for later steps.
- Add actions, such as Send email with the fields you choose, or Update record to tag the submission as coming from the form.
- Test every step, then switch the toggle from OFF to ON.
Each trigger is scoped to one table, so you can't select several forms in one trigger. If an automation isn't firing, the wrong form is usually selected. The trigger is optional, since forms submit without it, but it's how you send customised notifications, including to people who aren't base collaborators, and the Actual run time token gives you a submission timestamp.
My verdict on Airtable forms
I'd use the form view for simple internal intake where your table already exists, because it builds itself in a minute. If you're starting something new, go straight to the form builder, since that's where Airtable is adding features. And skip native forms altogether if you need multi-page or save-and-resume. For the basics of bases and views, here's my guide to using Airtable, and here's what Airtable free includes before you plan around the paid-plan features.
A form that files itself and sends the right email is a small automation that saves hours, and it's the kind of workflow I build with teams. I run AI training and workshops for teams, and help businesses with AI enablement, AI automation and GEO, which is about getting your business seen and cited in AI answers. Most of that work is with SaaS marketing teams and small businesses. Here's how we can work together.
Frequently asked questions
Can Airtable forms have multiple pages?
No. Airtable forms can't currently be split or paginated. Native forms are single-page.
Can an Airtable form update an existing record?
Not natively. Each submission creates a new record, though linked records and automations can be used as a workaround.
Can I remove Airtable branding from a form?
On paid plans you can remove the Airtable label, but you can't remove all Airtable branding or add your own custom branding in the Airtable UI.
Do I need an automation for every Airtable form?
No. Forms submit without one. The When a form is submitted trigger is only for workflows you want to run after a submission.
Can I create an Airtable form on mobile?
No. The mobile apps don't let you create forms. To submit one, use the share link in your device's browser.
