Update based on field(s)
Last updated
Last updated
When using , Data Fetcher can use unique fields (like an ID
field) from your API response to intelligently match and merge data with existing records in your output view. This prevents data from being written to the wrong records and preserves any existing relationships or custom record values.
Navigate to the request screen in Data Fetcher.
Scroll down to the bottom and click to open the Advanced settings.
Under Write Mode, ensure Update is selected.
Under Update Based on Field(s), select the field from your output table that contains unique values.
You can select multiple fields if needed for matching.
Important: Data Fetcher only looks at records in the output view, not the entire output table. If Airtable filters on your output view prevent Data Fetcher from finding matching records, duplicate records will be created instead.
Recommendation: Create a dedicated, locked view with no filters to use as your output view.
Let's say your current Airtable output view contains:
229
Orange Hat
5
107
Purple Skirt
10
Your API returns this updated data:
692
Blue T-Shirt
7
229
Orange Hat
10
107
Purple Skirt
17
Data Fetcher updates records by position, resulting in:
692
Blue T-Shirt
7
229
Orange Hat
10
107
Purple Skirt
17
The problem: The first record that was originally linked to "Orange Hat" is now associated with "Blue T-Shirt". Any existing relationships, comments, or custom field values are now tied to the wrong item.
Data Fetcher matches records using the unique Item Id field, resulting in:
229
Orange Hat
10
107
Purple Skirt
17
692
Blue T-Shirt
7
The result: Existing records are properly updated while preserving their identity and relationships. New records are added separately.
Choose a unique field when your API response contains records that should update specific existing records based on a common identifier.
Choose multiple fields when there is no unique identifier, but a combination of field values will always be unique.
Set to 'None' when running on multiple records where the position in the Run on Multiple Records table should determine which output record gets updated.