Airtable Schema Diff - Compare & Monitor Bases
Pricing
from $0.05 / base diffed
Compare two Airtable bases field by field, or snapshot one base and see exactly what changed since last run. Renames are reported as renames, not as a delete plus an add. Read-only token, schema.bases:read only - no record access.
A read-only Airtable personal access token. Only the schema.bases:read scope is needed — this Actor never reads a single record. Create one at airtable.com/create/tokens and add each base you want under Access.
Leave this empty to see a worked example. The Actor then compares two bundled sample bases instead of your own, and every row it writes is marked source="sample". That run is free.
Compare two bases checks every base below against one template base, so you can see how far copies of the same template have drifted apart.
Track one base over time stores a snapshot of each base and compares it against the snapshot from the previous run. The first run of any base stores its snapshot and reports no changes, because there is nothing yet to compare it against.
Airtable base IDs, one per line. Paste the whole base URL if that is easier — the ID is taken out of it. Leave empty to use every base the token can see.
[]The base everything else is compared against. Only used when comparing two bases. Leave it empty to use the first base listed above, which lets you paste the template first and its copies after it.
Kinds of change that will not be reported. The defaults hide the churn that every base produces on its own — someone hiding a column, dragging a field, recolouring a dropdown — so the output stays worth reading on a daily schedule.
[ "fieldDescriptions", "viewFieldVisibility", "fieldOrder", "viewOrder", "selectColors"]Drop changes milder than this. Leave it at Low to see everything; the output is sorted worst first either way.
The named key-value store that holds one snapshot per base, used when tracking a base over time. Snapshots are overwritten each run, one record per base. Change this only to keep two schedules from sharing snapshots.
Produce a self-contained web page per base listing every change, worst first, ready to send to whoever owns the base. The link appears on that base's summary row.