Airtable: Use "Field ID" instead of "Field Name"
Fabio Oliva
Can you please upgrade the airtable integration to use the ID instead of the name? Airtable + Integromat is super powerful but the moment someone changes the Field Name, everything gets screwed up. Zapier, for example, uses the field id and not the name.
-----------------------
REPLY: Our modules have advanced parameter 'Use Column ID' which addresses this problem. Use column ID instead of column name for mapping. This enable persistency over column name change. Changing this value will break all existing mappings in this scenario.
Log In
Autopilot
Merged in a post:
Default Airtable field mapping should use “Use Column ID = Yes”
Sergio Fandila
In Airtable modules, Make currently maps fields using the field’s Name by default. This is fragile because renaming a field in Airtable breaks the mapping inside the scenario.
Make already provides a more robust option: “Use Column ID = Yes”, which forces the module to reference the Airtable Field ID instead of the Name. This ensures that field renaming never affects existing automations.
However, this option must be manually enabled for every single Airtable module. It is easy to forget, especially in larger scenarios or when working across teams.
Proposal:
Set the default Airtable module behavior to “Use Column ID = Yes”. The Name-based mapping can remain available as an optional override when needed.
Benefits:
- Field renaming no longer breaks scenarios.
- Dramatically improved stability for complex Airtable-based systems.
- Lower maintenance overhead and fewer hidden failure points.
- Aligns Make with Airtable’s best practice of using stable Field IDs.
This small default-setting change would significantly increase reliability for all Airtable integrations.
K
Katerina Benova
Hi Fabio Oliva, please see the advanced parameter in our modules (click on 'Show advanced settings' to display it). This should solve the problem with the labels changes.