Overview
This node acts as a webhook trigger for Airtable events, allowing workflows to respond automatically when changes occur in an Airtable base. It registers a webhook on a specified Airtable base and listens for various types of data changes such as record updates, field modifications, or metadata changes.
Common scenarios where this node is beneficial include:
- Automating notifications or actions when new records are added or updated in Airtable.
- Syncing Airtable data changes with other systems in real-time.
- Triggering workflows based on specific types of changes or sources within Airtable (e.g., only changes made via the API or by users).
For example, you could use this node to start a workflow that sends an email whenever a new record is added to a particular table, or to update a CRM system when certain fields change.
Properties
| Name | Meaning |
|---|---|
| Base ID | The ID of the Airtable base to register the webhook for. |
| Data Types | The types of data to watch for changes. Options: • Table Data (record and cell value changes) • Table Fields (field changes) • Table Metadata (table name and description changes) |
| Record Change Scope | The ID of the table or view to watch for changes. Leave empty to watch the entire base. |
| Advanced Options | A collection of optional filters and settings: • Change Types: Only generate payloads for specific change types (Add, Remove, Update). • From Sources: Only generate payloads from specific change sources (e.g., Automation, Client, Public API). • Include Cell Values In Field IDs: Comma-separated list of field IDs to always include values for, regardless of whether they changed. • Include Previous Cell Values: Whether to include previous cell values in the webhook payload. • Include Previous Field Definitions: Whether to include previous field definitions in the webhook payload. • Watch Data In Field IDs: Comma-separated list of field IDs to watch for changes. |
Output
The node outputs JSON data representing the webhook payload received from Airtable. This payload contains detailed information about the changes detected according to the configured filters, including:
- Changed records and their cell values.
- Field changes if subscribed.
- Metadata changes like table names or descriptions if subscribed.
- Optionally, previous cell values and previous field definitions if enabled.
The output is structured as a JSON array with one element per webhook event, suitable for further processing in n8n workflows.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Airtable to authenticate API requests.
- Needs network access to Airtable's API endpoints.
- Uses cryptographic verification (HMAC SHA256) to validate incoming webhook signatures using a secret provided by Airtable during webhook registration.
Troubleshooting
- Webhook not triggering: Ensure the webhook was successfully created and registered on the correct Airtable base. Check that the Base ID is correct and that the node has valid API credentials.
- Invalid signature errors: If webhook payloads are ignored due to invalid signatures, verify that the secret used for HMAC validation matches the one returned by Airtable when creating the webhook. Also, ensure the raw request body is correctly passed for signature verification.
- No data received: Confirm that the data types and filters (change types, sources, field IDs) are set correctly to capture the desired events.
- API errors during webhook creation: These may be caused by incorrect permissions or invalid Base ID. Verify API credentials and base access rights.