One webhook for your whole Airtable base
Stop registering a webhook per table. With base-wide events you watch every record change — or every schema change — across an entire base with a single registration. Payloads stay granular, so you always know exactly what changed.
Watch every record change
New, updated, and deleted records in all tables of the base — one registration. Outgoing events stay granular: create, update, delete, each with the table and record that changed.
Watch every schema change
Tables and columns created, renamed, retyped, or deleted anywhere in the base. Outgoing events: table_create, table_update, table_delete, column_create, column_update, column_delete.
Pick exactly the right scope
Base-wide is the broadest end of the same scope spectrum. Trigger on as much or as little as you need.
| Scope | Registration event | Fires on |
|---|---|---|
| Single column | record_update (+ columns) | Updates that touch the fields you chose |
| Single table | record_create, record_update, record_delete | Record changes in one table |
| Table & column structure | table_*, column_* | Schema changes (one table or the whole base) |
| Entire base — records | base_records_change | Every record change in every table |
| Entire base — schema | base_schema_change | Every table & column change in the base |
Real-time
Events fire the moment data or structure changes — no polling, no Airtable scripts.
Granular payloads
The base-wide type never appears in the payload — you always get the concrete event, table, and record.
Less to maintain
Add a table tomorrow? It’s covered automatically. One registration instead of one per table.
How it works
- Create a free account and connect Airtable using a Personal Access Token.
- Add a webhook and choose Base Record Changes (all tables) or Base Schema Changes (all tables/columns).
- Select your base and enter the webhook URL from Make, Zapier, n8n, or your own app.
- For base record changes, optionally enable Coalesce rapid updates to group fast edits to the same record and save tasks.
Full details in the base-wide events guide. Already know your tool? Make, Zapier, n8n.
- Drop-in for existing per-table consumers — same payload shape.
- Coalescing keeps task usage down on busy bases.
Record event payload
{
"id": "notification-id",
"event": "create",
"recordId": "recXXXX",
"tableId": "tblXXXX",
"baseId": "appXXXX",
"fields": {},
"meta": {
"source": "client",
"occurredAt": "2026-06-06T17:44:14.321Z",
"user": {
"id": "usr...",
"name": "Test User",
"email": "test.user@example.com"
}
}
}Schema event payload
{
"id": "notification-id",
"event": "column_create",
"tableId": "tblXXXX",
"baseId": "appXXXX",
"column": {
"id": "fldXXXX",
"name": {
"current": "New Column"
},
"type": {
"current": "singleLineText"
}
},
"meta": {
"source": "client",
"occurredAt": "2026-06-06T17:44:14.330Z"
}
}Base-wide Airtable webhooks — FAQ
What is a base-wide Airtable webhook?
A single webhook registration that watches an entire Airtable base instead of one table. base_records_change fires on record changes in every table; base_schema_change fires on every table and column change. You no longer have to register and maintain one webhook per table.
Do outgoing payloads still tell me which table and record changed?
Yes. The registration type (base_records_change) never appears in the payload — you always receive the concrete event that occurred (create, update, delete, table_create, column_update, …) together with the baseId, tableId, and recordId or column. Consumers built for per-table webhooks keep working unchanged.
What is the difference between base_records_change and base_schema_change?
base_records_change watches row-level data — new, updated, and deleted records across all tables. base_schema_change watches structure — tables and columns being created, renamed/retyped, or deleted across the base.
Can I still watch just one table or a single column instead?
Absolutely. You can scope a webhook to a specific table, and for updates you can narrow it to specific columns so it only fires when the fields you care about change. Base-wide is simply the broadest end of the same scope spectrum.
Will I get duplicate webhooks if I also have table-specific webhooks?
Yes. A base-wide webhook and a table-specific webhook for the same change are independent registrations, so each delivers. Pick one scope per downstream automation to avoid double processing.
Watch your whole base in one step
Generous free tier. Upgrade anytime.