Overview
This node is an Instant Airtable Trigger that listens for real-time events from Airtable bases and tables via webhooks. It triggers workflows instantly when records are created, updated, or deleted in a specified Airtable table. This is useful for automating processes based on changes in Airtable data without polling.
Common scenarios:
- Automatically syncing Airtable record changes to other systems.
- Sending notifications or alerts when specific records are updated.
- Triggering downstream workflows when new records are added.
- Auditing or logging changes made to Airtable tables.
Practical example:
You can configure this node to watch a particular Airtable base and table for record updates. When a record is updated, the node triggers and outputs detailed information about the changed fields, including previous values if desired. This output can then be used to update a CRM, send an email, or perform any other automated action.
Properties
| Name | Meaning |
|---|---|
| Base Name or ID | Select the Airtable base to monitor. You can choose from a list or specify an ID using an expression. |
| Table Name or ID | Select the table within the chosen base to monitor. Options depend on the selected base. |
| Fields to Watch For Changes | Choose specific fields to watch for changes. Only changes in these fields will trigger the workflow. Can be left empty to watch all fields. |
| Extra Fields to Include in Output | Additional fields whose values should be included in the output payload alongside the changed fields. |
| Include Previous Cell Values? | Boolean option to include previous values of changed fields in the output, allowing comparison between old and new data. |
| Event Types | Select which event types to listen for: record creation, update, and/or deletion. Multiple can be selected. |
| Additional Fields | A collection of optional filters and settings: - Data Types: Filter payloads by type of change (table data, fields, metadata). - From Sources: Filter changes by their source (e.g., client, automation). - Source Options: JSON string for advanced filtering by form page or view IDs. - Watch Schemas of Field IDs: Watch schema changes for specific field IDs. |
Output
The node outputs an array of JSON objects representing the detected changes in Airtable. Each object includes:
- Details about changed records, fields, or metadata depending on the event.
- The
tableIdwhere the change occurred. - Information about the user who made the change (
userId,userName,userEmail) if available. - Timestamp of the change.
- If configured, previous cell values before the change.
- Additional fields as requested in the configuration.
The output does not include binary data; it is purely JSON structured data describing the Airtable changes.
Dependencies
- Requires an API key credential for Airtable with permissions to access the specified base and tables.
- The node uses Airtable's webhook API, so the Airtable account must support webhook creation.
- n8n workflow must be accessible via a public URL to receive webhook calls from Airtable.
- No additional external dependencies beyond Airtable API and n8n environment.
Troubleshooting
- Webhook creation failure: Ensure the API key has sufficient permissions and the base/table IDs are correct.
- No triggers firing: Verify that the webhook URL is publicly accessible and correctly registered in Airtable.
- Empty payloads: Check that the event types and fields to watch are properly configured; if too restrictive, no events may match.
- JSON parsing errors in Source Options: The "Source Options" field requires valid JSON syntax; invalid JSON will cause errors.
- Permission errors: Confirm the API key is valid and not expired.
- Rate limits: Airtable API rate limits may affect webhook payload retrieval; consider retry logic or reducing event frequency.