Overview
This node is an Instant Airtable Trigger that listens for real-time events from Airtable bases via webhooks. It triggers workflows when records in a specified Airtable base and table are created or updated, allowing automation based on changes in Airtable data.
Common scenarios where this node is beneficial include:
- Automatically processing new records added to an Airtable table.
- Reacting to updates in existing records to synchronize data with other systems.
- Monitoring specific fields within records to trigger workflows only when relevant data changes.
For example, you could use this node to trigger a workflow that sends notifications whenever a new customer record is added or when the status field of a project record is updated.
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 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 are watched. 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 to subsequent nodes. |
| Include Previous Values | Boolean option to include previous values of fields in the output. Useful for comparing before/after states of updated records. |
| 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 records that triggered the webhook event. The structure includes:
- Details of each changed record filtered by the selected table and fields.
- For each record, the output contains:
- Field values as per the "Fields to Include in Output" selection.
- Metadata about who made the change (user ID, name, email) if available.
- Timestamp of the change event.
- Previous field values if "Include Previous Values" is enabled.
The output is provided as an array of JSON objects, each representing a changed record with enriched metadata.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Airtable to authenticate API requests.
- Needs proper configuration of the Airtable base and table permissions to allow webhook creation and data access.
- The node uses Airtable's webhook API endpoints to create, check, and delete webhooks dynamically.
- The node depends on n8n's webhook infrastructure to receive incoming HTTP POST requests from Airtable.
Troubleshooting
- Webhook Creation Failures: Errors during webhook creation may occur due to invalid base/table IDs, insufficient permissions, or network issues. Verify credentials and resource selections.
- No Payloads Received: If the webhook triggers but no payloads are returned, ensure that the Airtable base and table have recent changes matching the selected event types and fields.
- Invalid Webhook Requests: The node expects webhook requests with specific body structure including
baseandwebhookidentifiers. Unexpected payloads will be ignored. - Missing Fields or Data: If output lacks expected fields, confirm that "Fields to Include in Output" is correctly set and that those fields exist in the Airtable table.
- Authentication Errors: Ensure the API key credential is valid and has access to the targeted Airtable base.
- Cursor Issues: The node tracks a cursor to fetch incremental payloads. If the cursor becomes out of sync, consider resetting the webhook or re-creating it.