How to Create and Customize Forms in Airtable

Airtable forms are the fastest way to capture structured data from people who do not have access to your base. Sales leads, job applicants, support requests, event signups, field inspections — every one of those is an Airtable form away from being inside your system instead of in someone's inbox.

In 2026 forms are still one of Airtable's most underrated features. They are free, they are part of the database (no separate Typeform syncing), and they support conditional logic, prefilled URLs, and embeds. This guide covers how to build a form, how to design it so people finish it, and the prefill and embed patterns that turn a basic form into a real intake system.

What an Airtable Form Actually Is

A form in Airtable is a view of a table. When someone submits the form, Airtable creates a new record on that table with the submitted values in the matching fields. That is the whole concept.

Because the form is bound to the table, two consequences fall out:

• The fields on the form are the fields on the table. Add a column to the table and it becomes available to add to the form. Rename a field and the form label updates (unless you have overridden it).
• Submissions can trigger automations. The When form is submitted trigger fires on every new submission and is how you send confirmation emails, route leads to a salesperson, or kick off a multi-step workflow.

This tight coupling is the difference between Airtable forms and a separate tool like Typeform or Google Forms. There is no sync, no Zap, no delay — the record is in the table the moment Submit is clicked.

Step 1: Creating Your First Form

Pick the table the form should write to. For a lead intake form that is usually a Leads or Contacts table. Then:

1. At the top left of the table, click the view switcher.
2. Click Create new view and choose Form.
3. Name the view something specific — Website Lead Form, not Form 1. You will have several forms eventually.
4. Airtable opens the form designer with every editable field on the table already on the form.
5. Drag fields off the form that you do not want respondents to see. Drag them back from the right-hand panel if you change your mind.
6. Click Share form in the top right and copy the public URL.

The form is live. Open the URL in an incognito window to test.

Step 2: Designing a Form People Actually Finish

The technical part of building a form takes two minutes. Making it complete-rate well is the part that matters. A few rules we apply on every client project:

Cut the form in half. The single highest-leverage change is removing fields. Each additional field drops completion rates measurably. Ask yourself for each field: do we need this now, or could the salesperson capture it on the first call? "Now" usually means name, email, company, and one qualifying question.

Set the right fields as required. Required fields show a red asterisk and block submission. Use this for the data the form is actually for. Do not require fields that are nice-to-have — make them optional and people will fill some of them in.

Write help text under tricky fields. Click a field in the form designer and add description text that appears under the label. Use it for fields where the respondent might not know what you mean, or to set expectations ("We respond within one business day").

Add a cover image and a logo. Click the cover area at the top to upload an image. Add your logo to the form header (paid plans). A form that looks like it belongs to your brand converts better than the default purple Airtable header.

Customize the submit button text and confirmation screen. Both editable in the form designer. The default "Submit" works; "Send my request" or "Get my quote" works better. The confirmation screen is your chance to set next steps — what happens now, how long until you reply.

Set a redirect URL (paid plans). Send respondents to a thank-you page on your own site after submitting. This is how you measure conversions in Google Analytics and trigger remarketing pixels.

Step 3: Conditional Logic — Branching Without a Branching Tool

Conditional logic lets you show or hide form fields based on what the respondent has already answered. It is the difference between a 30-field form that looks intimidating and a 30-field form that feels like 6.

To set it up:

1. Open the form view and click a field you want to show conditionally.
2. Toggle Show field only when conditions are met.
3. Add one or more conditions referencing other fields on the form.
4. Multiple conditions can be combined with AND or OR.

Common patterns:

Conditional fields are evaluated live as the respondent fills the form, so the form expands and contracts as they answer. Conditional logic requires a Team plan or higher.

Step 4: Prefilled Form URLs — The Power Move

A prefilled URL is a form URL with field values appended as query parameters. Visit the URL and the form opens with those fields already filled in. This is how teams send personalized forms at scale.

The format:

https://airtable.com/app123/shr456?prefill_FieldName=Value&hide_FieldName=true

• prefill_FieldName populates the field
• hide_FieldName=true hides it from the respondent so they cannot edit it
• Spaces in field names URL-encode as %20 or +
• Special characters (&, =, ?) need to be URL-encoded

Example. A renewal form pre-filled with the customer's email and account ID:

https://airtable.com/app123/shrABC?prefill_Email=jane%40acme.com&hide_Email=true&prefill_Account+ID=ACC-4012&hide_Account+ID=true

Jane opens the link, the form already knows who she is, and she only sees the questions you actually need her to answer.

Generating prefilled URLs in bulk. Add a formula field on the table that builds the URL using CONCATENATE and ENCODE_URL_COMPONENT. Then drop those URLs into a mail merge or an automation that emails each customer their unique link.

Prefilling linked record fields. You must pass the record ID (starts with rec...), not the display name. Find it by right-clicking a record and copying the record URL — the last segment is the ID.

Prefilling multi-select. Use a comma-separated list: prefill_Tags=Hot,Enterprise.

Step 5: Embedding the Form on Your Website

Click Share form → Embed this form on your site. Airtable gives you an iframe snippet.

<iframe
  class="airtable-embed"
  src="https://airtable.com/embed/shr123ABC?backgroundColor=blue"
  frameborder="0"
  width="100%"
  height="533"
  style="background: transparent; border: 1px solid #ccc;"
></iframe>

Paste it into:

• Webflow — Add an Embed element and paste the snippet
• WordPress — Custom HTML block in Gutenberg
• Framer — Embed component
• Squarespace — Code block
• Notion — /embed and paste the iframe URL

The embedded form inherits your form's styling. The iframe is responsive at width="100%"; adjust the height to match the number of fields.

Caveats. Free and Team plan forms show a small "Made with Airtable" footer in the embed. To remove it entirely you need the Business plan. For a fully white-labeled experience, many teams use Fillout or Softr — they write to Airtable via the API and let you fully control the design.

Step 6: Wiring Forms to Automations

A submitted form is just a created record. That means every automation pattern available on record creation works for forms too.

Send a confirmation email.

1. Create an automation with trigger When form is submitted (pick the form view).
2. Add a Send Email action.
3. Use the triggering record's email field as the recipient.
4. Personalize the body with {{Name}} and {{Project Type}}.

Route by field value. Use the When record matches conditions trigger instead. Set conditions like Source = Website Form AND Budget >= 5000 and route only those to a Slack channel for the sales team. The condition trigger is more precise than the form trigger because it can apply different actions to different submissions.

Tag and assign. Use a script action that looks at the submitted data and assigns the lead to a salesperson based on territory, deal size, or industry. See the scripting guide for the pattern.

Sync to a CRM. Pipe submissions to HubSpot, Salesforce, or Pipedrive via Make or Zapier. Airtable becomes the intake layer, the CRM stays the system of record.

Field Types That Behave Differently on Forms

Most field types render exactly as you would expect. A few have quirks worth knowing about:

Common Mistakes

We see the same form mistakes on every rescue project.

Letting form fillers create linked records they shouldn't. Turning on "Allow form fillers to create new records" on a Client linked field means every misspelling — "Acme", "Acme Inc", "acme inc." — creates a new client record. Either turn it off and route submissions through an automation that matches existing clients, or accept the cleanup work.

Forgetting the form is a view. A form view has filters and a field order just like a grid view. If you set a filter on the form view (which Airtable lets you do for the underlying records the form view "shows"), it does not affect submissions — the form does not show records, it creates them. But the field visibility and order do matter and are different from your grid view.

No spam protection. Public forms get scraped. For high-traffic forms, add a honeypot field (a hidden field that bots fill in; you delete records where it has a value) or front the form with a tool that includes a CAPTCHA. Airtable does not include native CAPTCHA in 2026.

Required-field traps inside conditionals. If a required field is conditionally hidden, no one ever fills it in and submission still succeeds (it is not visible to be required). If you need the data, do not conditionally hide a required field — make two forms instead.

Not testing in incognito. A form looks fine when you are signed into Airtable. Always test the share URL in a private window so you see exactly what respondents see.

Form Builder Comparison: Airtable vs Alternatives

For most teams, native Airtable forms are the right default — they are free, they live with the data, and they support automations natively. Move to Fillout or Tally when you need full branding, payments, or more advanced logic.

Where to Go Next

Once your form is collecting submissions, the next two steps are usually automating the follow-up and exposing the data internally. See the Airtable automation guide for the trigger and action patterns, and the Interface Designer guide for building a staff-facing view of the submissions.

For Airtable's official documentation on forms, the Forms support article covers every option in the form designer. To capture data and immediately route it through a multi-step automation, the Make automation guide shows the full pattern.