How to Trigger an Airtable Automation with a Webhook from a Zap

A practical field guide from Automation Ace.

How to Trigger an Airtable Automation with a Webhook from a Zap

Most Airtable-plus-Zapier integrations run in one direction: Airtable holds the data, Zapier watches for changes and takes action elsewhere. But there is a useful reverse pattern — using a Zap to trigger an Airtable automation. This enables Zapier to act as the orchestrator for events originating in other systems, with Airtable's automation engine handling the downstream record updates, script runs, or notifications on the Airtable side. The mechanism is Airtable's "When webhook received" automation trigger, which gives any external system — including Zapier — the ability to fire an Airtable automation on demand.

Why Trigger Airtable from Zapier?

Zapier's native Airtable actions (Create Record, Update Record, Find Record) are direct API calls — they read and write data, but they cannot trigger Airtable's own automation logic. If your Airtable base has automations that handle complex record updates, run scripts, send internal notifications, or chain together multiple Airtable-side operations, Zapier cannot invoke those automations natively. The webhook trigger pattern closes that gap: Zapier sends a webhook, Airtable receives it and runs whatever automation logic you have configured.

Common scenarios where this pattern is useful:

• A form submission arrives in Zapier (via Typeform, JotForm, or a native form trigger), and you want Airtable to run a complex multi-step automation in response — not just create a record
• An event in a CRM (HubSpot, Salesforce) triggers a Zap, and you want Airtable to update linked records across multiple tables using its automation scripting capabilities
• A Zapier Schedule trigger (time-based) should kick off a periodic Airtable automation that queries and updates records
• You want Airtable to run a JavaScript script (via Airtable's Run Script action) in response to an external event routed through Zapier

Step-by-Step: Triggering an Airtable Automation from a Zap

Step 1: Create the Airtable automation with the webhook trigger

1. In your Airtable base, open the Automations tab and click + New automation.
2. For the trigger, choose When webhook received.
3. Airtable generates a unique webhook URL for this automation — copy it. It will look like https://hooks.airtable.com/workflows/v1/genericWebhook/[unique-id].
4. Use the test section to send a sample payload so Airtable can learn the shape of the data Zapier will send. You can do this by making a test POST request from any HTTP tool, or by completing Zapier's setup and running a test Zap.

Step 2: Design the Airtable automation actions

After the webhook trigger, add the Airtable automation actions that should run when the webhook fires. The payload data Zapier sends is available as dynamic values in the automation action fields. Common actions to chain after the webhook trigger:

• Find records — look up existing records using a value from the webhook payload (e.g., an email address or record ID)
• Update record — modify a field on a found record using payload data
• Create record — add a new record with fields populated from the payload
• Run script — execute a JavaScript script that can use the payload data and make complex multi-record changes
• Send email / Send Slack message — notify team members based on the inbound event

Step 3: Add a Webhooks by Zapier action to your Zap

1. In the Zap where you want to trigger the Airtable automation, add an action step and choose Webhooks by Zapier.
2. Select POST as the action event.
3. In the URL field, paste the Airtable webhook URL you copied in Step 1.
4. Set Payload Type to JSON.
5. In the Data section, add the key-value pairs you want to send to Airtable. Use data mapped from earlier Zap steps — for example, a contact's email, a record ID, or a status value that Airtable's automation will use to find and update the right record.

For more detail on configuring Webhooks by Zapier POST actions, including authentication and JSON body setup, see how to use APIs in Zapier steps.

Step 4: Test the connection

1. Run a test of the Webhooks by Zapier action in the Zap editor. Zapier sends the POST request to Airtable's webhook URL.
2. In Airtable, check the automation's run history — you should see the webhook trigger fire and the payload data appear.
3. If Airtable shows the payload fields correctly, map them into your automation actions and complete the Airtable-side logic.
4. Enable the Airtable automation and publish the Zap.

Structuring the Webhook Payload

Airtable's webhook trigger reads the JSON body of the POST request. Design your payload to include the data Airtable needs to execute its automation actions without making additional API calls. If Airtable needs to find a record, send the lookup field value (e.g., email, external ID). If Airtable needs to update specific fields, send those field values in the payload so the automation can map them directly.

A minimal payload example for a lead processing automation:

{
  "lead_email": "contact@example.com",
  "lead_name": "Jane Smith",
  "source": "typeform",
  "score": "85"
}

Airtable's automation then uses lead_email to find the matching record and score to update it — all without Zapier needing to know the Airtable record ID in advance.

When to Use This Pattern vs. Native Airtable Actions in Zapier

Use Zapier's native Airtable actions (Create Record, Update Record) when the operation is simple — write one or a few field values to a specific record. Use the webhook trigger pattern when:

• The Airtable-side logic is complex (multiple record lookups, conditional branching, script execution)
• You want Airtable's automation to handle its own internal notifications or follow-up actions
• The Airtable automation already exists and you want Zapier to act as one of several possible triggers for it
• You need Airtable to run a script that is not expressible through Zapier's field-mapping actions

The webhook trigger pattern makes Airtable a true automation participant rather than just a passive database. When Airtable's automation engine handles its own record logic and Zapier handles routing between external systems, each tool does what it is designed for — and the integration is more maintainable than trying to replicate Airtable's automation logic entirely within Zapier.

For the reverse direction — using Airtable to trigger Zaps instantly via webhook — see how to trigger Zaps instantly from Airtable. For a broader overview of Airtable and Zapier integration patterns, see the Airtable integrations guide. For help designing a bidirectional Airtable-Zapier workflow, talk to Automation Ace.