Has anyone found a reliable way to handle CSV imports in Airtable when the source files are inconsistent?
We currently have a custom CSV import flow where users upload files containing customer and account data. Before importing into Airtable, we need to validate required fields, data types, and business rules, then map the uploaded columns to our internal schema.
The biggest challenge is dealing with files that don’t follow the expected format. Different customers use different column names, some required fields are missing, date formats vary, and duplicate records need to be identified before the import proceeds. We also need to provide users with clear error messages so they can fix issues without contacting support.
Right now, most of this logic is custom-built and becoming difficult to maintain. Every time we add a new import type or validation rule, it requires engineering effort, and edge cases frequently introduce bugs.
What’s the best approach for validating, mapping, and processing imported data in Airtable while keeping the user experience clear and scalable?