Overview
This node acts as an instant trigger for Airtable events by using webhooks. It listens for changes in a specified Airtable base and table, such as record creation or updates, and triggers workflows accordingly. This is useful for automating processes that depend on real-time data changes in Airtable, like syncing records to other systems, sending notifications when data changes, or updating dashboards.
For example, you could use this node to:
- Trigger a workflow whenever a new record is added to a specific Airtable table.
- React instantly when certain fields in a record are updated, enabling dynamic automation based on those changes.
Properties
| Name | Meaning |
|---|---|
| Base Name or ID | Select the Airtable base to monitor. You can choose from a list or specify an ID via expression. |
| Table Name or ID | Select the table within the chosen base to watch for changes. Options depend on the selected base. |
| Fields to Watch Names or IDs | Specify which fields to monitor for changes. If left empty, all fields may be considered. You can select multiple fields by name or ID. |
| Fields to Include in Output Names or IDs | Choose which fields' data should be included in the output payload. This controls what information about changed records is passed downstream. |
| Include Previous Values | Boolean option to include previous values of fields in the output, allowing comparison between old and new data. |
| Event Types | Select which event types to listen for: "Record Created" (new records) and/or "Record Updated" (existing records modified). You can select one or both. |
Output
The node outputs JSON data representing the changes detected by the webhook. The structure includes:
- An array of objects, each corresponding to a changed record matching the configured filters.
- Each object contains:
- Field values as per the selected "Fields to Include".
- Metadata about who made the change (user ID, name, email) if available.
- Timestamp of the change.
- Additional details about the change depending on configuration.
If the node is configured to include previous values, these will also be part of the output, enabling workflows to compare before/after states.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Airtable with permissions to access bases, tables, and manage webhooks.
- Needs network access to Airtable's API endpoints.
- The node uses Airtable's webhook system, so the workflow must be accessible via a public URL for webhook callbacks.
- No additional external dependencies beyond Airtable API and n8n environment.
Troubleshooting
- Webhook Not Triggering: Ensure the webhook was successfully created and the workflow is active. Check that the base and table IDs are correct and that the Airtable API key has sufficient permissions.
- No Payloads Received: This can happen if no relevant changes occurred since the last cursor or if the webhook was deleted externally. Recreate the webhook or verify the webhook ID stored in static data.
- Invalid Webhook Request: If the incoming webhook payload lacks expected fields (
base,webhook), it will be ignored. Confirm Airtable is sending valid webhook notifications. - API Errors When Creating Webhook: Verify API credentials and network connectivity. Also, check rate limits or permission issues on the Airtable side.
- Fields Not Loading: When selecting fields, ensure the base and table parameters are set correctly; otherwise, field loading methods return empty lists.
Links and References
- Airtable API Documentation
- n8n Expressions Documentation
- Airtable Webhooks Guide (for understanding webhook setup and payloads)