I am creating an Airtable database integrated with a Fillout inquiry form, for a sole proprietor advising business.
My objective was straightforward:
When an Inquiry contains a Contact and an Organization, update that Contact's Organization field with the Organization associated with the Inquiry.
The current interface required interpreting Record ID as the specific Contact to update, selecting an Inquiry Contact field to supply that record, and then understanding that another Organization field represented the value to place into the Contact's Organization field. The repeated use of field names while the instructions referred to records made the workflow unnecessarily ambiguous.
Recommendation: Use Task-Oriented Language in the “Update Record” Automation
The Update Record automation interface relies heavily on database terminology such as Record ID, Fields, and dynamic field tokens. While technically accurate, the terminology does not clearly communicate the sequence of decisions a user must make. This can make a simple automation unnecessarily difficult to configure, particularly when working with linked records.
Recommendation: Supplement technical database terminology with task-oriented questions that describe what the user is actually configuring.
| Current wording | Recommended wording |
|---|---|
| Table | Which table contains the record you want to update? |
| Record ID | Which record in this table should be updated? |
| ID of the record to update. To update a record from a previous step, use the + menu to choose the step and its Record ID. Must correspond to the selected table. | Select the specific record to update. To identify it dynamically, choose a linked record from a previous automation step and use its Record ID. |
| Fields | What field(s) should be changed? |
| Organization (selected field) | Field to update: Organization |
| Choose record(s) to link to, by entering record IDs or names | What should Organization be set to? Select the Organization record from a previous step or enter a record ID/name. |
| Generate a preview | Preview the record and changes before updating |
Ideally, Airtable could also provide a plain-language summary before testing:
This automation will:
Find the Contact referenced by Inquiry Contact in the triggering Inquiry, and set that Contact's Organization to the Organization referenced by the same Inquiry.
That single sentence would have made the configuration immediately understandable.
The underlying functionality works well once configured. The opportunity is to make the interface reflect the user's intent rather than requiring users to translate their intent into Airtable's internal database terminology. This would make Automations substantially more approachable without removing the technical terminology advanced users may need.