How to use an Airtable form to update a record

Airtable forms create records. That's it. Every submission adds a new row to your table. There is no built-in way to load an existing record into a form, let a user change a few fields, and save those changes back.

This is a problem that hits almost every Airtable workflow eventually. You build a project tracker, a CRM, an inventory system. You need people to update their own records. And then you discover that native forms can only insert, never update.

Here's what people try, what actually works, and how to set up update forms that connect directly to your base.

Need update forms now? Filla builds edit forms that load existing Airtable records, let users modify fields, and save changes back to your base. No code, no middleware. Start free →

Why Airtable forms can't update records

Airtable forms were designed for one purpose: collecting new data. When someone opens a native Airtable form, every field is blank. There is no mechanism to pass a record ID, load existing values, or write changes back to a specific row.

This isn't a limitation on certain plans. It applies to Free, Team, Business, and Enterprise. The form feature simply doesn't support editing.

The result: teams that need record updates end up building workarounds or giving users direct access to the base. Neither option scales well.

Common workarounds (and their limits)

Workaround 1: Give users base access

The simplest approach. Add collaborators to the base and let them edit records directly in grid or gallery view.

Problems:

Every editor needs a paid seat on Team plan or above
Users can see and modify any record, not just their own
Accidental deletions happen constantly
The Airtable interface is overwhelming for non-technical users

Workaround 2: Use Airtable Interfaces

Airtable Interfaces let you build custom layouts with editable fields. You can create a record detail view where users click into a record and change values.

This is Airtable's closest native answer to the "update form" problem. It works, with caveats:

Users need at least "commenter" access to the base (which requires a seat on paid plans)
Interfaces don't work well as external-facing forms
You can't share a direct link that opens a specific record for editing
The layout options are limited compared to a dedicated form builder
No conditional logic on which fields appear during editing

For internal teams already paying for Airtable seats, Interfaces are a reasonable option. For anything external or public-facing, they fall short.

Workaround 3: Automations that match and update

Some teams create a "submit changes" form that collects the record identifier (like an email or order number) plus the updated values. Then an automation runs: find the matching record, update its fields.

This technically works but creates several problems:

Users can't see the current values before changing them
There's no validation that the record exists before submission
You need a unique identifier that users actually know
Building and maintaining the automation takes real effort
Debugging failed matches is painful

Workaround 4: Scripts and the Airtable API

You can build a custom frontend that calls the Airtable API to fetch a record, display its fields in a form, and PATCH the changes back. Some teams use Airtable Scripting extensions or external tools like Softr or Stacker.

This works but requires:

Development time to build and maintain
API key management
Custom error handling
A hosting solution for the frontend

For teams with engineering resources, this is viable. For everyone else, it's not practical.

How Filla handles record updates

Filla is a form builder made specifically for Airtable. One of its core features is the ability to create update forms, sometimes called edit forms, that load an existing record's data and let users modify it.

Here's how it works:

1. Connect your base

When you connect your Airtable base to Filla, it reads your table schema: field names, types, options, linked records. No manual field mapping.

2. Create an update form

Instead of a blank "create" form, you set the form mode to "update." This tells Filla to load existing record data when the form opens.

Each record gets a unique form URL. When a user opens that link, the form loads with the record's current values pre-filled. They see what's already there, change what they need, and submit. The changes write back to that specific record in Airtable.

4. Control which fields are editable

You choose which fields appear on the update form. Some fields can be read-only (visible but not editable). Others can be hidden entirely. This means you can show a user their order status without letting them change the order total.

Use cases for Airtable update forms

Status updates and progress tracking

A project management base where team members update task status, add notes, or log hours. Each person gets a link to their assigned tasks and updates fields without touching the base directly.

Profile and contact editing

A membership database where members can update their own contact info, preferences, or profile details. Send each member a personalized edit link. They see their current data and change what's outdated.

Inventory adjustments

A warehouse team that needs to update stock counts, locations, or condition notes. Workers scan or click a link for a specific item and update the relevant fields on their phone.

Client intake updates

A consulting firm where clients fill out an initial intake form, then return later to update their information as the engagement progresses. The update form shows what they submitted previously and lets them revise it.

Event RSVP changes

An event management base where attendees can modify their RSVP: change meal preference, update guest count, or cancel. One link per attendee, pre-filled with their current selections.

Approval workflows

A request system where a manager opens a form pre-filled with the request details and only needs to set the approval status and add comments. The rest of the fields are read-only.

Step-by-step: common update form patterns

Pattern 1: Self-service profile editing

Setup: You have a Contacts table with Name, Email, Phone, Address, and Preferences fields.

Create an update form in Filla connected to your Contacts table
Include all fields you want users to edit
Set Name and Email as read-only (visible but not changeable)
Make Phone, Address, and Preferences editable
Generate unique edit links for each contact
Send the link via email or embed it in a portal

When a contact opens their link, they see their name and email (confirming they have the right record) and can update their phone, address, and preferences.

Pattern 2: Weekly status reports

Setup: You have a Projects table with Project Name, Status, Percent Complete, Blockers, and Next Steps fields.

Create an update form showing Status, Percent Complete, Blockers, and Next Steps
Set Project Name as read-only
Share each project's edit link with the assigned team member
Team members open the link weekly, update their fields, and submit

No automation needed. No risk of someone editing the wrong project. The form only shows and edits the record tied to that link.

Pattern 3: Order modification

Setup: You have an Orders table with Order Number, Customer, Items, Quantity, Shipping Address, and Status fields.

Create an update form for the Orders table
Set Order Number, Customer, and Items as read-only
Make Quantity and Shipping Address editable
Only show the form when Status equals "Processing" (use conditional logic to hide the submit button for shipped orders)
Share the edit link in the order confirmation email

Customers can modify quantity or shipping address while the order is still processing, but can't touch anything once it ships.

Airtable Interfaces vs. Filla update forms

Feature	Airtable Interfaces	Filla Update Forms
Edit existing records	Yes	Yes
Requires Airtable seat	Yes	No
Works for external users	Limited	Yes
Direct link to specific record	No	Yes
Conditional field visibility	No	Yes
Custom branding	Limited	Yes
Read-only fields	Yes	Yes
Mobile-friendly	Partial	Yes
Embeddable	No	Yes

Interfaces work well for internal teams that already have Airtable seats. Filla is the better option when you need external users to update records, want direct links per record, or need conditional logic during editing.

Things to consider when building update forms

Permissions matter. Decide who can edit what. Not every field should be editable by every user. Use read-only fields and conditional visibility to control access.

Unique links prevent mistakes. Record-specific URLs mean users can only edit their own record. No searching, no accidental edits to the wrong row.

Validation still applies. Just because a record already exists doesn't mean updated values should skip validation. Required fields, format checks, and range limits should still apply on update forms.

Audit trails help. Consider adding a "Last Updated" or "Updated By" field to your table. Filla can populate these automatically so you know when a record was last modified through a form.

FAQ

Can Airtable forms update existing records?

No. Native Airtable forms can only create new records. Every form submission adds a new row to your table. There is no built-in option to load an existing record into a form for editing. To update records through a form, you need either Airtable Interfaces (for internal users with base access) or a third-party tool like Filla.

How do I send someone a link to edit a specific Airtable record?

Airtable itself doesn't offer shareable edit links for individual records (the record URL requires base access). With Filla, each record gets a unique form URL. When someone opens that link, the form loads with the record's current data pre-filled. They edit the fields you've made available and submit the changes directly back to your base.

What is the difference between Airtable Interfaces and update forms?

Airtable Interfaces are internal dashboards that let base collaborators view and edit records within a custom layout. They require an Airtable seat and base access. Update forms built with Filla are standalone forms that work for anyone with the link, no Airtable account needed. Filla also supports conditional logic, custom branding, and embeddable forms, which Interfaces do not.

Can I control which fields are editable on an update form?

Yes. In Filla, you choose exactly which fields appear on the update form. Fields can be set to editable, read-only (visible but not changeable), or hidden entirely. This lets you show context like an order number or customer name without allowing modifications to those fields.

Start building update forms

If your workflow needs record updates through forms, native Airtable won't get you there. Interfaces cover basic internal editing, but anything external, conditional, or link-based requires a different approach.

Filla connects directly to your Airtable base, supports update forms out of the box, and gives you control over which fields are visible and editable.

Create your first update form free →

Airtable Form Update Record: Edit Existing Data