When should you update instead of creating a new record?
Use an update workflow when someone is correcting or completing an existing entity: a project brief, event registration, or supplier profile. Use a create workflow when the submission represents a genuinely new entity. Make that decision before designing the questions, because the same-looking form can produce different database results.
For a fictional studio, the first brief creates a project and a later form changes its deadline and delivery notes. The update should preserve the original project identity. Creating another project would split the conversation and make a dashboard appear to have more work than the studio actually accepted.
Configure the documented update path
Open the Airtable integration of a connected Fillout form and select Update record. Put its provided formula in an Airtable formula field, then publish the form. Each record's generated link opens its prefilled values.
Without the record ID, Fillout creates a new record. Treat the generic form URL and the record-specific update link as separate entry points. Check which one your email template, button, or portal actually sends.
Limit the fields the update is allowed to change
In the studio example, expose the requested delivery date and notes. Keep the internal project owner, billing status, and approval decision outside the intended client-editing workflow. Write this allowed-field list beside the integration mapping so a later form edit does not silently expand its scope.
Decide what a blank answer means for each field: preserve the current value, clear it, or reject the submission. Verify the integration's actual behavior with sample data. An edit form that appears to leave a field untouched can still produce a surprising result if the mapping writes an empty value.
| Input case | Expected business result | Evidence to inspect |
|---|---|---|
| Valid record link | Only the intended project changes | Record ID and before/after fields |
| Missing record ID | Document whether creation is acceptable | Record count and integration response |
| Blank optional note | The agreed preserve-or-clear behavior | Stored field value |
| Repeated submission | No unintended extra project or downstream work | Records and automation activity |
| Link forwarded to someone else | Access matches the information's sensitivity | The actual access control and exposed data |
Treat a prefilled link as part of the access design
A URL identifying a record explains which record the form should load. It does not, by itself, establish who is entitled to view or edit that record. Check the access controls available for your chosen Fillout configuration and the place where links are distributed. Do not infer authentication from the fact that a URL is difficult to guess.
Use harmless fictional records for the trial. Open a forwarded link in a separate browser context and examine what data is visible before submission. If the required restriction cannot be demonstrated, redesign the handoff before using the form for sensitive customer information.
Why not use an Airtable form alone?
Airtable documents that its forms create new records and describes a separate-table-and-automation workaround for updates, alongside other interface and portal options. Fillout's documented update mode is another route to evaluate. Compare the complete access model and ongoing maintenance, rather than assuming an extra form service is necessary for every Airtable workflow.
Why does my update form create a duplicate?
Check that the record-specific link delivered the expected ID; a missing ID creates a new record. Then inspect downstream automations, since another process could create the duplicate after a correct update. Trace one sample through the whole workflow before changing several settings at once.
Sources and editorial method
Official sources linked in this guide were checked on October 28, 2026. Recommendations and fictional examples are editorial analysis, not hands-on product tests or customer results. Features, prices, and plan limits can change; confirm the current documentation before choosing a plan or implementing a workflow.