Read the Airtable schema
Base, table, field types, required fields, linked records, and select options shape the import template.
Impora checks incoming files against the Airtable schema you already use, so operators can fix problems before records are created or updated.
Designed for repeatable Airtable operations, not one-off cleanup.
The gap
Required fields, select options, and linked records need to match the live Airtable base
Spreadsheet headers drift between teams, suppliers, and systems
Native imports create cleanup work when validation happens after the write
Operators need a clear hold, fix, approve, and retry path
Validation path
Base, table, field types, required fields, linked records, and select options shape the import template.
Headers are matched to Airtable fields and can be reviewed before repeat use.
Rows are validated for missing values, invalid formats, constrained fields, and linked-record matches.
Operators see what passed, what failed, and what needs correction before Airtable is updated.
Product proof
The validation screen gives operators a visible gate between incoming files and the Airtable base.
Errors are visible before anything reaches Airtable.

Common errors
The useful part of validation is not the warning itself. It is telling the uploader what changed, why Airtable would reject or damage the row, and how to correct it before import.
Missing required value
A field that operators rely on is blank in the source row.
Fill the value in the CSV or Excel file, or update the template if the field should no longer be required.
Select option mismatch
The file contains a single-select or multi-select value that does not exist in Airtable.
Choose an existing Airtable option or add the approved option in Airtable before rerunning the import.
Invalid email or URL
A contact, supplier, or link field does not match the format Airtable expects.
Correct the source value and rerun validation instead of letting bad contact data enter the base.
Date format mismatch
The source date is ambiguous or formatted differently from the Airtable field.
Normalize the date in the source file, especially when files mix US, AU, or ISO-style dates.
Linked record not found
A linked-record column names a value that Impora cannot match to the target table.
Fix the spelling, create the missing linked record where appropriate, or review the linked-record mapping.
Duplicate import key
Two rows appear to target the same existing record or external identifier.
Deduplicate the source file or confirm which row should be treated as the latest version.
Capabilities
Validate against Airtable field types, required fields, select options, and linked records.
Save mapping and validation decisions so recurring imports do not restart from scratch.
Failed rows are reported clearly so teams can fix the source file and retry.
Operator trust
Teams know what was accepted, what was held, and what needs to happen next.
FAQ
Yes. Templates are built from your Airtable base and table structure so validation follows the destination schema.
Yes. The same saved template rules can be used for direct upload, folder automation, and email handoff workflows.
Failed rows are held for review and recovery instead of being silently written into Airtable.
Uploads, folder automation, email handoff, exports, and recovery in one governed layer.