How to Receive Incoming Webhooks in Airtable Automations

An incoming webhook lets another system start an Airtable automation. Airtable gives the automation a receiving URL.

This differs from Airtable sending a webhook to Make. Read that outgoing webhook example for the reverse direction.

Receive a small test event

Create an automation with the When webhook received trigger. Copy its receiving URL. Send a JSON POST from a private test tool using this illustrative event:

{
  "eventId": "test_profile_001",
  "type": "profile_submitted",
  "profileId": "demo_profile_001",
  "name": "Alex Rivera"
}

Inspect the trigger's sample data. Map profileId and name into a test intake table. Use eventId to check for an existing submission before creating another record. Airtable documents the incoming trigger. Keep its URL private and rotate it if exposed.

Handle provider events through a verified receiver

The original video covers Webflow forms, Memberstack signups, and Stripe payments. For Stripe, checkout.session.completed is a documented Checkout event. However, Airtable's incoming trigger does not support signature verification. Send Stripe events to a receiver that verifies the signature before forwarding permitted fields to Airtable. Do not grant access or credit an account merely because an unverified POST says a payment succeeded. Stripe's fulfillment guidance covers payment status and delayed payment methods.

Start with the harmless test event. Add provider data only after verifying its origin and duplicate handling.

Original video

Watch the original video on How to Receive Incoming Webhooks in Airtable Automations.

For the basic event flow, understand webhook triggers before connecting a provider.