Watch · 2-minute setup
Pick the Airtable table, map the fields, set the subject token and sender allowlist, then hand out the inbox address. Here is the whole thing in one pass.
Rather read it? See the control surface below ↓
A real handoff, every week
Twelve suppliers email invoice spreadsheets to a shared AP address. Someone used to open each one, copy it into Airtable, and hope the columns matched. Here is what changed once the address was an Impora inbox.
The outcome, one quarter in
The real control surface
A unique, shareable address maps to a saved Airtable table and its rules. Copy it and hand it out.
Impora confirms the sender is on your allowlist and the subject token matches, with SPF/DKIM verification, before opening any attachment.
CSV and Excel attachments are parsed and imported; anything else is quarantined automatically.
Passing emails import on their own. The connector shows last received, last success, and last failure, with nothing to run by hand.
The other direction
Impora doesn’t only pull data in. Send Airtable views out as scheduled CSV or Excel files, and, when you want a review loop, let recipients edit the attachment, reply, and have their changes flow straight back into the right template.
Trusted senders only
Email is convenient, but easy to fake. Impora authenticates every message with the same SPF and DKIM signals your mail provider trusts, and fails closed the moment they don’t line up.
Every message is checked for SPF and DKIM alignment. Spoofed or misaligned email is rejected before anything is opened, genuine authentication, not a readable "From:" field.
Beyond authentication, a message must come from an allowlisted address or domain and carry your subject code. Miss either and nothing imports.
You forward files to an Impora address. Impora never logs into, reads, or stores your mailbox, only the messages sent to that inbox.
Required fields, formats, select options and linked records are checked with the exact rules your direct uploads use, nothing gets a looser pass by email.
Accepted, rejected, and quarantined messages all appear in run history, so an email channel stays as auditable as any other intake lane.
Fail-closed by default. If authentication fails, the sender isn’t on the allowlist, or the subject code is missing, Impora imports nothing and replies to nothing, silence is the safe default. Every attachment that does pass is still validated against your Airtable rules before a single row is written.
Yes. Senders just email a file to the inbox address. Airtable access stays limited to your operators, no seats or logins for the people sending data.
CSV and Excel attachments (.csv, .xlsx, .xls) are processed for import. Any other attachment type is quarantined automatically rather than imported.
Every message is authenticated (SPF/DKIM), must carry the required subject token, and must come from an allowlisted address or domain. Anything that misses a check is rejected before an attachment is parsed.
Impora verifies SPF and DKIM on every message and rejects anything spoofed or misaligned before it is opened. Combined with the sender allowlist and subject code, the inbox fails closed, nothing imports and nothing replies unless every check passes.
Yes. Impora sends Airtable views out as scheduled or triggered CSV/XLSX files by email. With the roundtrip flow, a recipient edits the attachment, replies, and their changes re-import to the matching template automatically.
Yes. The inbox address accepts manual forwards and Gmail/Outlook auto-forwarding rules alike, so a system that already emails a report can feed Airtable with no extra steps.
You choose. Turn on automatic imports to process messages as they arrive, or leave it manual and run a check on the waiting messages when you are ready.
Valid rows import and failed rows are held with an error report. The sender can correct just those rows and resend, and it all shows up in run history.