The complete guide

Airtable Webhooks

Airtable webhooks let your other tools react the moment your data changes — a new record, an edit, a deletion. This guide explains how Airtable webhooks work, and how Simplified Webhooks gives you instant, real-time events in Make, Zapier, n8n, or at any URL — without hosting an endpoint or writing code.

Does Airtable have webhooks?

Yes — Airtable has a native webhooks API. But it’s built for developers: you have to host a public endpoint, register the webhook, refresh it before it expires (Airtable webhooks expire after 7 days), and decode Airtable’s raw change-payload format. Most people don’t want to run that infrastructure.

Simplified Webhooks handles the entire lifecycle for you and delivers a clean event — to a no-code tool or any URL — so you get the benefit of Airtable’s webhooks without the developer overhead.

Events you can listen for

New records

Fire the instant a record is created in a table — no polling delay, no missed rows.

Updated records

Get the changed fields with both previous and current values, so you know exactly what changed.

Deleted records

Catch deletions reliably — something polling triggers simply cannot do once the row is gone.

Webhooks (push)

Airtable pushes an event the instant something changes. Your automation runs immediately and only when there’s real work to do — efficient and real-time.

Polling (scheduled scans)

Tools like Make and Zapier scan Airtable on a schedule. That adds minutes of delay, burns operations on every check, and can’t reliably detect deletions.

Ways to connect Airtable webhooks

A clean, predictable payload

Every event is plain JSON with the event type, the base, table, and record IDs, and the changed fields — including previous and current values for updates. No decoding Airtable’s raw change format.

Building something solid? Read our Airtable webhooks best practices guide.

Example webhook payload

{
  "id": "notification-id",
  "event": "update",
  "recordId": "recXXXX",
  "tableId": "tblXXXX",
  "baseId": "appXXXX",
  "fields": {},
  "meta": {
    "source": "client",
    "occurredAt": "2026-01-01T00:00:00.000Z"
  }
}

Airtable webhooks FAQ

Does Airtable have webhooks?

Yes. Airtable has a native webhooks API, but it is built for developers — you have to host a public endpoint, register the webhook, refresh it before it expires (Airtable webhooks expire after 7 days), and parse Airtable's change-payload format yourself. Simplified Webhooks runs all of that for you and delivers a clean event to your tool or URL.

Are Airtable webhooks real-time?

With Simplified Webhooks, yes — events are pushed the moment a record is created, updated, or deleted, typically within seconds. This is different from polling triggers (like Make or Zapier scanning Airtable on a schedule), which add minutes of delay and consume operations on every check.

Can I get a webhook when an Airtable record is deleted?

Yes. Simplified Webhooks has dedicated events for new, updated, and deleted records. Deletions are notoriously hard to catch with polling because the row is already gone — webhooks capture them reliably.

Do I need to write code to use Airtable webhooks?

No. Connect Airtable with a Personal Access Token, then either add a trigger module in Make, Zapier, or n8n, or point the webhook at any URL you control. No endpoint to host, no webhook lifecycle to manage.

What does an Airtable webhook payload look like?

Each event is clean JSON with the event type, the base/table/record IDs, and the changed fields (including previous and current values for updates) — no need to decode Airtable’s raw change format.

Get real-time Airtable webhooks

Connect a base and start receiving instant events for new, updated, and deleted records. Free to get started.

Airtable Webhooks — The Complete Guide | Simplified Webhooks