Three ways to fire an export
Same engine, same run history. Just a different way to start it.
Daily, weekly, or a custom interval where the connector supports scheduling. Set it once and the snapshot goes out on its own.
Let an Airtable automation decide when the file is ready. Call the export webhook with a generated secret where a template has a trigger configured.
Run on demand for a one-off report, a quick test, or recovery. The same export, fired by hand whenever you need it.
Watch it work
See a scheduled export send clean Airtable records to a connected Google Drive folder, validated and logged on every run.
What goes out
Choose the Airtable table or a specific view from your saved template. Impora pulls that data, writes a clean snapshot, and delivers it, so downstream teams get exactly the slice they expect.
Source: Deals table · Closed-won view
Where exports land
Point an export at a connected cloud folder or an inbox. Same snapshot, whichever destination the recipients expect.
Drop timestamped snapshots into a shared Drive folder your team already opens.
Deliver into a document library your organisation governs and controls.
Send backups to a personal or team OneDrive folder on every run.
Attach the CSV or Excel file and email it straight to a distribution list.
Not buried in a script
Exports live in the same operator console as imports, so you can see what went out, when it ran, and whether delivery completed.
When to reach for it
Send a CSV or Excel copy of a table or selected view to the folder or inbox where a downstream team expects it, on a cadence, hands-off.
Keep a recoverable history of what Airtable looked like at a point in time, delivered to a folder you control.
Let an Airtable automation decide when the outbound file is ready and call the export webhook to fire it.
Three ways: on a schedule (daily, weekly, or a custom interval where the connector supports it), from an Airtable automation via a webhook where a template has an export trigger secret configured, or manually on demand.
Yes. An export can use a full table or a selected view from the saved template, so recipients get exactly the slice of data they need.
To a connected cloud folder (SharePoint, OneDrive, or Google Drive) or to email recipients, where those destinations are configured on the template.
Exports are written as CSV or Excel (.xlsx). Timestamped filenames make backup-style archives straightforward to keep.
Every export appears in run history alongside imports, showing the trigger, destination, row count, time, and whether delivery completed, so nothing is hidden in a script.
Yes. Import and export are separate connector modes on the same template, which is what makes roundtrip workflows, data out and edits back in, possible with distinct inbound and outbound lanes.