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 change, including previous values if desired. This output can then be used to update a CRM, send emails, or perform other automated tasks.
Properties
| Name | Meaning |
|---|---|
| Base Name or ID | Select or specify the Airtable base to watch for changes. |
| Table Name or ID | Select or specify the Airtable table within the chosen base to monitor. |
| Fields to Watch For Changes | Choose specific fields to monitor for changes. Only changes in these fields will trigger the workflow. |
| Extra Fields to Include in Output | Additional fields whose values should be included in the output payload beyond those that changed. |
| Include Previous Cell Values? | Whether to include the previous values of changed fields in the output, allowing comparison before and after the change. |
| Event Types | The types of record events to listen for: - Record Created - Record Updated - Record Deleted |
| Additional Fields | A collection of optional filters and settings: - Data Types: Filter payloads by types of changes (table data, fields, metadata). - From Sources: Filter changes by their origin (e.g., user, automation, API). - Source Options: JSON string for advanced source filtering. - Watch Schemas of Field IDs: Monitor 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 the changed records, fields, or metadata depending on the event.
- The
tableIdindicating which table the change belongs to. - Information about who made the change (
changedBy), including user ID, name, and email if available. - A timestamp of when the change occurred.
- If configured, previous cell values before the change.
- Additional fields as requested in the configuration.
If binary data were involved (not indicated here), it would represent attachments or files related to the records, but this node focuses on JSON payloads describing data changes.
Dependencies
- Requires an API key credential for Airtable with permissions to access the specified base and tables.
- Needs webhook support enabled in Airtable and proper webhook URL configuration.
- Uses Airtable's REST API to manage webhooks and fetch payloads.
- n8n environment must allow incoming HTTP POST requests at the webhook path configured by this node.
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 accessible publicly and Airtable can reach it.
- Empty payloads: Check that the event types selected match actual changes happening in Airtable; also confirm filters like fields to watch or sources are not too restrictive.
- JSON parsing errors in source options: Make sure the "Source Options" field contains valid JSON.
- Authentication errors: Confirm the API key credential is valid and not expired.
- Rate limits or API errors: Airtable enforces rate limits; excessive webhook calls may cause failures.