Google Drive
Shared partner folders and recurring operational uploads
Trigger
Folder watch
New files enter a monitored intake lane with the same saved template rules.
Integrations
Connect the places your data lives. Control how it reaches Airtable.
Impora turns Drive, SharePoint, OneDrive, email, uploads, exports, and webhooks into one governed operating layer for Airtable data movement.
Integration control plane
Choose source, mode, template, and recovery path.
Drive
Folder watch
SharePoint
Folder watch
OneDrive
Folder watch
Email handoff
Import
Export
Roundtrip
1supplier-price-list.csvValidating
2april-stocktake.xlsxReady
3partner-upload.csvBlocked
Destination
Airtable view or recipients
Success path
_processed / sent export
Recovery path
_errors report / run history
One control plane
Folders, email, upload links, exports, and webhooks all follow the same operator model.
Provider-native intake
Keep files where teams already work: Drive, SharePoint, OneDrive, email, or direct upload.
Visible run state
Operators can see what ran, what failed, and what needs to be fixed before the next pass.
Airtable-aware routing
Each integration is connected to saved Airtable template rules instead of one-off scripts.
Intake channels
Give every source a controlled door into Airtable.
The integration choice should match how the file arrives, who owns it, and what the operator needs to recover when something goes wrong.
SharePoint
Microsoft environments with governed document libraries
Trigger
Folder watch
Teams can keep files in SharePoint while Airtable stays protected downstream.
OneDrive
Smaller teams and owner-managed import folders
Trigger
Folder watch
Owner-managed folders become reliable repeatable intake points.
Email inbox
Suppliers, scanners, and external senders
Trigger
Inbound and outbound email
Import, export, or roundtrip CSV handoffs without giving senders a login or folder access.
Direct CSV and Excel upload
Use the same template rules for one-off files, quick tests, or contributors who do not need a connected folder.
Automation modes
Each connector can do more than receive files.
Impora supports the operating patterns around Airtable: automatic imports, scheduled exports, Airtable-triggered webhooks, direct sends, and separated roundtrip handoffs.
Watched intake
Automatic import
Watch a folder or inbox, validate each row, and only send clean data into Airtable.
Trigger
Folder or inbox
Outcome
Clean rows enter Airtable
1File arrives
2Schema check
3Row validation
4Airtable import
Run state stays visible from trigger to recovery.
Timed run
Scheduled export
Run saved Airtable exports on a set cadence, then deliver the file by folder or email.
Trigger
Saved schedule
Outcome
CSV delivered on time
1Schedule runs
2View queried
3CSV created
4File delivered
Run state stays visible from trigger to recovery.
Webhook
Airtable-triggered export
Let an Airtable automation call Impora exactly when a workflow is ready to export.
Trigger
Airtable action
Outcome
Export logged visibly
1Airtable trigger
2Webhook call
3Data exported
4Delivery logged
Run state stays visible from trigger to recovery.
Two lanes
Roundtrip handoff
Keep intake and outbound files in separate lanes so every movement stays traceable.
Trigger
Inbox + outbox
Outcome
Movement stays traceable
1Inbound import
2Airtable updates
3Outbound export
4History retained
Run state stays visible from trigger to recovery.
Operator console
The proof is in the control surface.
Operators need the parts that matter after setup: run history, mode controls, schedule, source, file, records, and status.
Run history by source
Import and export modes
Scheduled exports
Partial run visibility
Run history
Know what moved, what failed, and when.
A connector is only useful if operators can see its runs. The run history view makes integration state visible across imports and exports.
1
Incoming
A file appears in a watched folder or email inbox.
2
Processing
Impora applies the selected template and run mode.
3
Processed
Clean files move forward with a visible run record.
4
Errors
Failed rows produce a report for recovery and re-drop.
The integration does not end at connection. It ends when the operator can see what happened.
Folder lifecycle
Integrations need a recovery path, not just a trigger.
When a source sends clean data, the file should move forward. When it sends broken data, the operator needs a report, a place to fix it, and a predictable way to retry.
Inbox/
incoming-price-list.csv
_processed/
_errors/
Recovery output
Failed rows generate an error report CSV so the source can be fixed and reprocessed without manual Airtable cleanup.
At a glance
Match the integration to the operational job.
The important question is not which logo is on the page. It is how the data enters, what checks run, and what happens when something is wrong.
Integration
Best for
Trigger
Modes / controls
Status
Google Drive
Team folders
Best for
Best when teams already collect files in shared Drive folders.
Trigger
Folder check / schedule
Modes / controls
ImportExportRoundtrip
Folder URL, view filter, schedule, webhook trigger
StatusAvailable
SharePoint
Governed libraries
Best for
Best for Microsoft environments and controlled document workflows.
Trigger
Folder event / webhook
Modes / controls
ImportExportRoundtrip
Inbox folder, outbox folder, view filter, run history
StatusAvailable
OneDrive
Owner-managed folders
Best for
Best for lean teams where one person owns the source folder.
Trigger
Folder event / schedule
Modes / controls
ImportExportRoundtrip
Folder picker, export view, schedule, recovery folders
StatusAvailable
Email inbox
External senders
Best for
Best when suppliers, scanners, or systems need to send files without login.
Trigger
Inbound / schedule / webhook
Modes / controls
ImportExportRoundtrip
Inbox alias, subject token, recipients, sender allowlist
StatusAvailable
Direct upload
One-off files
Best for
Best for quick tests, ad-hoc files, and contributor upload links.
Trigger
Manual
Modes / controls
Import
Guided upload flow and approval step
StatusAvailable
HubSpot sync
CRM graph
Best for
Best when Airtable and HubSpot need association-aware sync across CRM objects.
Trigger
Sync loop
Modes / controls
Contacts, Companies, DealsAssociationsConflicts
Identity matching, linked records to associations, conflict review
StatusPrivate beta waitlist
Email inbox
Let external files move by email.
The email inbox connector gives suppliers and systems a low-friction way to send and receive CSV files while operators keep recipients, allowlists, subject tokens, schedules, and run history in Impora.
External sources
Not every sender belongs in your storage or Airtable account.
Email handoff gives external contributors a familiar submission path while also letting operators send scheduled exports and roundtrip files without opening access to Airtable or shared storage.
Unique inbox address per template
Sender allowlist and subject token
Recipients, templates, schedules, and Send export now
Private beta waitlist
Airtable and HubSpot sync for your CRM graph.
Join the free waitlist for association-aware Airtable <-> HubSpot sync across Contacts, Companies, Deals, and linked-record relationships.
Contacts, Companies, Deals
Linked records to associations
Conflict review queue
Identity matching
Start with the workflow that breaks most often.
Connect a folder, test a direct upload, or join the HubSpot sync waitlist if CRM reliability is the bigger problem.