Airtable webhooks
Test and debug Airtable webhooksfor record changes and base updates
Keep bases and downstream tools in sync. Hooklistener captures every Airtable webhook so you can see payload changes and debug record updates before they break ops workflows.
How Airtable webhooks work
| Where to create it | Webhooks API only: POST https://api.airtable.com/v0/bases/{baseId}/webhooks with a notificationUrl and a specification. Up to 10 webhooks per base; base creator permission required. |
|---|---|
| Notification body | A short ping with the base id, webhook id and timestamp, not the changes. Fetch the changes afterwards with the list webhook payloads endpoint. |
| Signature header | X-Airtable-Content-MAC: hmac-sha256= followed by the hex HMAC-SHA256 of the body, keyed with the base64-decoded macSecretBase64 returned once at creation. |
| Timeout and retries | Respond with 200 or 204 within 25 seconds. Failed pings are retried up to 13 times with exponential backoff starting at 10 seconds (about one day), then notifications are disabled. |
| Expiry | Webhooks created with personal access tokens or OAuth tokens expire after 7 days unless refreshed with refresh webhook or list webhook payloads. |
Sources (checked November 2026)
See every Airtable event your app receives
Airtable webhooks are the backbone of lightweight ops automation, from CRM syncs to content pipelines. When a record change fails to propagate, the tools relying on that data drift out of sync.
Hooklistener captures each Airtable delivery with its payload so you can inspect field changes, follow automation timing and forward events to staging before a production rollout.
Why teams use Hooklistener for Airtable
Schema drift across bases
Field names and linked records change over time, and a small update quietly breaks a larger workflow.
Silent sync failures
Airtable automations can fail without enough context to tell what was sent and when.
Multi-base coordination
Keeping marketing, ops and product bases aligned is messy when each team sees a different part of the event trail.
How Hooklistener helps with Airtable webhooks
Diff two Airtable deliveries
Compare two captured Airtable record updates to catch a renamed field or changed linked record, and let anomaly detection flag the schema drift on its own.
Request history with timing
Keep each Airtable automation request with its body, headers and arrival time (history by plan), so a silent sync failure has the context it was missing.
Shareable debugger links
Send the marketing, ops or product owner of a base a link to the captured Airtable request so every team reads the same event.
Try it: point Airtable at a free webhook URL or run a test with the webhook tester.
Airtable automation plays that save time
CRM and lead sync
Keep Airtable, HubSpot and sales ops tools aligned when a record changes, so no qualified lead is lost.
Content and editorial workflows
Follow publishing statuses, approvals and task updates across editorial databases without manual follow-up.
Inventory and operations tracking
Send stock, vendor or fulfillment changes into internal systems before they become reporting errors.
Replay a failed webhook without re-triggering the provider
Once a delivery is captured, you can resend its exact headers and body to localhost, staging or production from the dashboard or through your coding agent over MCP, so the provider never has to fire a new event. Replay is on Pro and above. Read the replay guide.
Comparing webhook debugging tools?
See how Hooklistener stacks up against webhook.site, RequestBin, Beeceptor, Hookdeck and ngrok in the best tools to capture and inspect webhook payloads, or read the head-to-head pages for Hooklistener vs ngrok and Hooklistener vs Beeceptor.
Frequently asked questions
Can I inspect Airtable record changes in Hooklistener?
Yes. Capture Airtable webhooks and inspect the full payload, including field updates, linked records and the time each delivery arrived.
Does this work with Airtable Automations?
Yes. Point an automation's webhook step at a Hooklistener endpoint to see exactly what it sends while you test changes.
Can I replay Airtable events to staging?
Yes. Replay is on Pro and above. Resend stored deliveries to local environments, QA endpoints or another tool to check sync behavior before release.
Is this useful for non-developers?
Yes. Ops and RevOps teams can open a shareable debugger link, compare payloads and see why a workflow fired without touching code.
Keep Airtable in sync
Capture and inspect every Airtable webhook so record changes stop getting lost between tools.