Airtable Webhook Trigger icon

Airtable Webhook Trigger

Handles Airtable events via webhooks

Overview

This node acts as a webhook trigger for Airtable events, enabling workflows to respond automatically when records in an Airtable base are created or updated. It listens for changes in specified tables and fields within an Airtable base and triggers the workflow with detailed information about those changes.

Common scenarios where this node is beneficial include:

  • Automating notifications or follow-up actions when new records are added to an Airtable table.
  • Syncing Airtable data changes with other systems or databases in real-time.
  • Monitoring specific fields in Airtable records and triggering workflows only when those fields change.

For example, you could use this node to trigger a workflow that sends an email alert whenever a new customer record is added or when the status field of an order 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 in the table to monitor for changes. If left empty, all fields are watched.
Fields to Include in Output Names or IDs Choose which fields' data should be included in the output payload when the webhook triggers.
Include Previous Values Boolean option to include previous values of changed fields in the output, useful for tracking what exactly changed.
Event Types Select which event types to listen for: "Record Created" (when a new record is added) and/or "Record Updated" (when an existing record is modified).

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 for the specified fields to include.
    • Metadata about who made the change (user ID, name, email), if available.
    • A timestamp indicating when the change occurred.
    • Previous values of fields if the "Include Previous Values" option is enabled.

If no relevant payloads are found, the node returns an empty result.

The node does not output binary data.

Dependencies

  • Requires an API key credential for Airtable to authenticate requests.
  • Depends on Airtable's webhook API to receive event notifications.
  • Uses internal helper functions to fetch bases, tables, and fields dynamically for property options.
  • Needs the workflow to expose a publicly accessible webhook URL for Airtable to send events.

Troubleshooting

  • Webhook Not Triggering: Ensure the webhook was successfully created in Airtable and the workflow's webhook URL is correctly set. Check that the selected base, table, and event types match the actual changes happening in Airtable.
  • No Payloads Received: This can happen if there are no recent changes after the last cursor position. Try making a test change in Airtable or resetting the webhook.
  • Error Creating Webhook: Verify that the API key has sufficient permissions and that the base and table IDs are correct.
  • Invalid Webhook Request: The node expects a specific payload structure from Airtable. If the request body is missing required fields like base or webhook, it will ignore the request.
  • Field Options Not Loading: Make sure the base and table parameters are set before selecting fields to watch or include, as these depend on prior selections.

Links and References

Discussion