How to Let Users Edit Existing Airtable Records with a Form
Airtable forms only create new records. That's the design. Every time someone fills out a native Airtable form and submits, a brand-new row appears in your table. There is no way to load an existing record, let the person update it, and save those changes back.
This single limitation blocks more real-world workflows than any other Airtable form constraint.
Need edit forms for Airtable? Filla lets respondents look up, pre-fill, and update their own Airtable records — no code, no middleware, no workarounds. Start free →
Why edit forms matter
Think about every workflow that requires a person to go back and update what they entered:
- A vendor updates their contact info in your supplier database
- A client reviews and approves the project brief you prepared
- A job applicant updates their CV after the first interview
- An event attendee changes their meal preference
- A team member updates their timesheet entry after a manager review
Every single one of these needs an edit form — a form that opens pre-filled with the person's existing data and saves changes back to the same record. Native Airtable forms can't do any of these.
What people try (and why it doesn't work)
Sharing Airtable base access. Some teams give respondents view access to the base so they can edit directly in the grid. This exposes your entire database, not just the person's own record. It's a privacy and data integrity problem.
Creating a new form for updates. Some teams build a separate "update" form that collects the same fields. Now you have duplicate records — one original, one update — and someone has to manually reconcile them.
Airtable automations to merge records. Some teams build complex automation sequences to find the original record, copy values from the update form, and delete the duplicate. It works until the automation breaks, which it will.
Airtable Interfaces. Interfaces can let authenticated users edit records, but they're a full portal product — significantly more complex to configure, not shareable as a simple link, and not designed for external respondents.
None of these is a form that works the way edit forms should work.
How Filla handles record editing
Filla adds a Login Page — an authentication gate you place at the front of any form. Respondents go through the login page first, identify themselves, and the form loads with their existing record pre-filled. When they submit, the record is updated, not duplicated.
The three verification modes
Filla gives you three ways for respondents to identify themselves:
Lookup mode. The respondent enters a value — typically their email address or order number — and Filla searches your Airtable table for a record that matches. If found, the record loads in the form. You choose which field(s) to match against.
This is the most flexible mode. You can use any field as the lookup key — email, phone number, customer ID, order number, project code. You can also require multiple fields to match (email AND date of birth, for example) for higher identity assurance.
Email mode. The respondent enters their email address. This mode is optimized for email-based identity: Filla finds the record where the email field matches what they entered. Simpler than Lookup for standard email-identified workflows.
Password mode. The respondent enters a shared password to access the form. This is appropriate for internal forms where everyone who has the password should be able to access it — not for external respondents who each have their own record.
Setting up a record edit form: step by step
Step 1: Create your form in Filla
Sign up at app.filla.io/signup, connect your Airtable base via OAuth, and select the table whose records you want to let respondents edit.
Step 2: Add a Login Page
In the form editor, click the + button in the page bar at the bottom to add a new page. Select Login Page as the page type.
A login page is automatically placed before the first form page — it's the gate respondents go through.
Step 3: Choose your verification mode
In the Login Page settings panel, select your verification mode:
- Lookup: Choose which field(s) the respondent enters to find their record. Filla adds those fields as inputs on the login page.
- Email: Choose the email field in your table. Filla adds a single email input on the login page.
- Password: Set a shared password. Filla hashes it. Respondents enter it to access the form.
Step 4: Add fields to your form pages
On the form pages that follow the login page, drag the fields you want respondents to be able to edit. When a record loads after login, these fields will pre-fill with the current values from that record.
You control exactly which fields are editable. Leave sensitive fields off the form entirely — they won't appear, and respondents can't modify them. Make certain fields read-only using the Read-only toggle in field settings — respondents can see the value but can't change it.
Step 5: Configure the Thank You page for edit mode
Click the Thank You page. In the sidebar, find Edit mode behavior. Choose what happens when a respondent submits an edit:
- Show thank you page: Display the standard confirmation after updating.
- Stay on form: Keep the form open with the record still loaded. Useful for forms that might need multiple edits in a session.
Step 6: Test with an existing record
Use the form's preview mode to test. Enter a lookup value that matches an existing record in your table. Verify that the form loads pre-filled with that record's data. Make a change, submit, and check your Airtable table to confirm the record was updated — not duplicated.
Per-record edit URLs: giving every record its own link
The login-based approach works when respondents know their lookup value. But sometimes you want to send people directly to their own pre-loaded form — no lookup step required.
Filla generates an Airtable formula for this. Here's how it works:
Get the per-record formula
In the Filla form editor, click the Share button. In the Share panel, find the Record edit links section. Filla shows you a formula:
"https://yourform.filla.io/" & RECORD_ID()
The exact URL will be your form's actual share URL. RECORD_ID() is the Airtable formula function that returns the unique ID of each record.
Add it as a formula field in Airtable
Go to your Airtable table. Add a new Formula field. Paste the formula Filla gave you. Name it something like "Edit Link" or "Update Form URL."
Airtable evaluates this formula for every row in the table. Each record gets a unique URL — its own direct edit link that bypasses the login page and opens the form pre-loaded with that specific record's data.
Use the formula field
Once the formula field exists, you can:
- Include it in confirmation emails: Airtable automations or Filla's confirmation email can reference this field, so every respondent receives a personalized edit link the moment they first submit.
- Display it in an Airtable Interface: Put the link in an interface page where team members can copy it and send it to the relevant respondent.
- Batch-send it to existing records: If you're migrating existing records and want to invite previous respondents to update their data, filter the table, pull the formula field values, and send.
Real use cases for edit forms
Client brief review
A freelancer collects project briefs from clients via an intake form. When the project scope changes, they send the client the edit link. The client opens the pre-filled form, updates the relevant fields, and submits. The updated record appears in Airtable immediately — no email thread, no copy-pasting, no version confusion.
Vendor contact updates
An operations team maintains a vendor database in Airtable. Each vendor has a record with their contact details, payment terms, and compliance documentation. Once a year, the team sends each vendor their edit link with a request to verify and update their information. Vendors click the link, update what's changed, and the database stays current without any manual entry.
Event attendee updates
An event coordinator collects registrations via a form. After registration, attendees get a confirmation email with an edit link. If they need to change their meal preference, accommodation request, or session selection before the event, they use the link — no need to contact the team, no need to re-register.
Employee record maintenance
An HR team uses Airtable to track employee information. New employees fill out an onboarding form. When personal details change — address, emergency contact, banking information — the employee can use their personal edit link to update their own record directly. The form shows only the fields relevant to self-service updates; payroll and HR-managed fields are hidden.
How edit forms compare across tools
| Capability | Native Airtable | Filla | Fillout |
|---|---|---|---|
| Edit existing records via form | No | Yes — login page + per-record URLs | Partial (workarounds required) |
| Pre-fill form from record data | No | Yes — automatic on login | Manual setup |
| Per-record URLs from Airtable formula | No | Yes — formula generated in Share panel | No |
| Authentication modes | N/A | Lookup, Email, Password | Limited |
| Control which fields are editable | N/A | Yes — per field | Limited |
FAQ
Can respondents edit their Airtable records with a native form?
No. Native Airtable forms only create new records. Every submission adds a new row. There is no built-in mechanism to load an existing record into a form, let a respondent modify it, and save those changes back to the original row. For edit forms connected to Airtable, use Filla.
Does the edit form create a duplicate record?
No. When a respondent submits through a Filla edit form (after passing the login page or clicking a per-record URL), Filla writes the changes back to the same Airtable record they loaded. The record is updated, not duplicated. In the Filla responses dashboard, updated submissions are marked with an "Update" badge to distinguish them from original submissions.
What if a respondent enters a lookup value that doesn't match any record?
When no matching record is found, the login page shows an error message. Respondents cannot proceed past the login page if their lookup value doesn't match. You can customize the error message to give them guidance — for example, "No record found for that email. Please check the address you used to register."
Can I prevent respondents from editing certain fields?
Yes. Fields you don't add to the form simply don't appear — respondents have no way to see or modify them. For fields you want to show (so respondents can see their value) but not allow editing, toggle Read-only on in the field settings panel. The value displays but the input is locked.
How do I send respondents their edit link automatically?
Add the per-record formula field to your Airtable table. Then reference that field in Filla's confirmation email (using variable text) or in an Airtable automation's Send email action. When the respondent first submits the form, the confirmation email they receive includes their unique edit link. Every future edit is one click away.