Airtable Webhook icon

Airtable Webhook

Triggers when Airtable records change via webhooks. The webhook is registered automatically when you activate the workflow, and deleted when you deactivate it. Webhooks expire every 7 days — use the Airtable Webhooks Refresh workflow to keep them alive.

Airtable Webhook

AI-generated

Summary

Listen for changes in a specified Airtable base and table via a dynamically registered webhook, triggering the workflow when records are created, updated, deleted, or when field schemas or table metadata change according to detailed filters.

Inputs

  • Base (required) — Select the Airtable base to watch for record changes.
  • Table (required) — Select the specific table within the base to monitor for changes.
  • View — Optionally scope the webhook to a particular view in the table; triggers when records enter or leave the view.
  • Change Types (required) — Choose which record change types (Add, Update, Remove) trigger the workflow. Defaults to all.
  • Fields to Watch — For 'Update' events, specify fields to watch for changes; leave empty to watch all fields.
  • Fields to Include in Output — Select fields whose values should always be included in the output, even if unchanged; 'All fields' includes every field.
  • Use Field Names — Toggle to use human-readable field names instead of Airtable's internal field IDs in the output.
  • Include Previous Values — For 'Update' events, choose whether to include previous values of changed fields in the output.
  • Advanced Options — Additional fine-tuning filters including which data types to watch (table data, fields, metadata), change sources, schema watching on specific fields, and inclusion of previous field definitions.

Output shape

a list of change event objects

The output contains one or more event objects describing the changes captured by the webhook, including event type (created, updated, deleted, field schema changes, metadata changes), record or field identifiers, changed data, the source of the change, user info if available, and timestamps. Field names or IDs appear based on user preference. If no new changes are detected at webhook firing, no items are emitted.

Links

Discussion