Read-only Airtable OAuth
Choose the exact bases Airhistory should protect.
Airhistory protects selected Airtable bases with read-only snapshots, field-level history, cloud folder backups, and safe restore to a new base.
Choose the exact bases Airhistory should protect.
Snapshot files live in your Google Drive or Dropbox.
Compare snapshots when records or fields change.
Get safe backup alerts without raw provider errors.
Why backup history matters
Keep an independent history for the moments native history cannot explain quickly enough.
Open a snapshot comparison instead of reconstructing edits from memory.
Use the previous snapshot as a clean reference before the next fix.
Snapshot
May 16, 10:42
Dashboard and email alerts keep backup problems visible.
Restore into a new Airtable base without overwriting the original.
Beyond manual exports
Automated snapshots, readable diffs, and alerts when history stops.
Back up only the Airtable bases you choose, with plan limits enforced before snapshots run.
Choose bases to back up
5 of 5Pick Google Drive or Dropbox destinations per selected base so backups are easy to find.
Cloud destination
snapshot-history.json
Written outside Airtable
Create a JSON snapshot on demand before imports, cleanups, or client handoffs.
Manual snapshot
Destination
Drive > Airhistory
File
snapshot.json
Captured
Just now
Tables
6
Snapshot saved
Review added, modified, deleted, and field-level changes between snapshots.
Save daily, weekly, or monthly launch schedules that run in the shared daily processing window.
Backup schedule
Status emails, failure alerts, lost-connection alerts, and dashboard warnings use safe labels only.
Backup needs attention
Safe failure email
No secrets or raw errors.
Pricing
Starter is the current self-serve launch plan. Professional and Scale open after higher-volume scheduled backup jobs are hardened.
For launch users backing up key Airtable bases.
$19/mo
For larger teams after launch capacity hardening.
$49/mo
For busy teams with many Airtable bases.
$99/mo
Security and limits
Built for snapshots, diffs, notification preferences, and new-base restore. Existing bases are not overwritten.
Connection tokens stay encrypted and never ship to the browser.
Backup files write to the Google Drive or Dropbox folders the user chooses.
The browser and emails avoid raw provider IDs, secrets, and record content.
Restores create a new Airtable base instead of overwriting the original.
Start with one read-only snapshot in your own cloud.