Skip to main content
Instead of registering separate webhooks for each event type, you can use base-wide events to monitor an entire Airtable base with one registration.

​
Overview

Registration eventWhat it watchesOutgoing payload event values
base_records_changeNew, updated, and deleted records in all tablescreate, update, delete
base_schema_changeTable and column create, update, and delete in the entire basetable_create, table_update, table_delete, column_create, column_update, column_delete
The registration event type (e.g. base_records_change) does not appear in outgoing payloads. You always receive the granular event that actually occurred.

​
Register via API

Use the Register Webhook endpoint and select the Watch Base Record Changes or Watch Base Schema Changes schema.

​
Base record changes

{
  "baseId": "appkGlXEiufQLn1Qd",
  "event": "base_records_change",
  "coalesceUpdates": true,
  "webhookUrl": "https://hook.eu1.make.com/your-unique-hook-id"
}
  • Do not pass tableId or columnId.
  • Set coalesceUpdates: true to group rapid updates to the same record into one webhook (saves Make/Zapier/n8n task usage).

​
Base schema changes

{
  "baseId": "appkGlXEiufQLn1Qd",
  "event": "base_schema_change",
  "webhookUrl": "https://hook.eu1.make.com/your-unique-hook-id"
}
  • Do not pass tableId, columnId, or coalesceUpdates.

​
Register via Dashboard

  1. Open the dashboard and click Add Webhook.
  2. Choose Base Record Changes (all tables) or Base Schema Changes (all tables/columns).
  3. Select the base and enter your webhook URL.
  4. For base record changes, optionally enable Coalesce rapid updates.

​
Important notes

Duplicate deliveries: If you also have table-specific webhooks (e.g. record_create on the same table), you will receive two webhooks for the same change.
High traffic: base_records_change on large bases can generate many webhooks. Use coalesceUpdates to reduce update bursts; it does not affect create or delete events.

​
When to use base-wide events

  • Sync pipelines that need every record change across a base without maintaining per-table webhooks.
  • Schema sync to external databases or documentation when any table/column change should trigger a rebuild.
  • Audit logging of all structural changes in a base.
For single-table or single-column precision, use the individual event types documented in Table Events and Column Events.