Airtable automation
Add New Testimonials to Airtable
Airtable automations can start when a webhook arrives, which makes it one of the few destinations that may need no middleware at all. StoryProof, from Pro, calls your URL for every new review. Whether Airtable can take that call straight depends on what the delivery looks like, and the test step will tell you.
- A base laid out for reviews before anything arrives
- The “When webhook received” trigger, tested properly
- When to put a middleware in front
Automation checklist
Set up the base and the webhook automation
Airtable will not let you move past the trigger until it has seen a request, so the StoryProof side comes in the middle, not at the end.
Nothing you tick leaves this page.
The problem, solved
Why reviews and campaign planning drift apart
- Problem 1
Briefs live in Airtable, proof lives elsewhere
Writers go hunting for a quote mid-brief and settle for whichever one they remember.
How StoryProof solves it
From Pro, each new review is sent out as it arrives, and an Airtable webhook automation can turn it into a record next to your briefs.
- Problem 2
The automation is stuck on its test
Airtable requires a successful request before the next step unlocks, and a manual test request does not show what StoryProof really sends.
How StoryProof solves it
Use StoryProof itself as the test: add the URL to your webhooks, leave one review, then run the test so the fields Airtable sees are the real ones.
- Problem 3
The base starts acting as the approval queue
Someone marks a record as good to use in Airtable, but the review was never approved for the site.
How StoryProof solves it
Keep approval in StoryProof, where nothing goes public until it is approved, and mirror only the outcome in the base with a status field or tags.
- Problem 4
A planner picks a review for the homepage in Airtable
Choosing it in the base does not put it on the site.
How StoryProof solves it
The widget decides what shows. You choose which approved reviews appear in each StoryProof widget, so the base records the plan and the widget carries it out.
- Problem 5
Webhooks are not included on our plan
Without them the base is filled by hand again.
How StoryProof solves it
Every plan shows an in-app alert when a review lands, which at least tells whoever maintains the base to add it.
In StoryProof
Run it end to end
Step 1 of 4
Shape the table
Decide the fields people will filter on, and add your own status field before any record exists.
Step 2 of 4
Create the webhook trigger
In Automations, add “When webhook received” and copy its URL.
Step 3 of 4
Send a real review
Paste the URL where your StoryProof settings list webhooks, leave one test review, and run the trigger test.
Step 4 of 4
Map, test and switch on
Add Create record, map the fields Airtable received, test it, and turn the automation on. If the trigger would not accept the request, place a middleware in front and repeat.
Before you start
Things to know first
No Airtable connector
StoryProof is not described here as an Airtable integration. A webhook automation, sometimes with a middleware in front, is the link.
The delivery may need reshaping
Airtable accepts a top-level JSON object or form data. This page does not say what StoryProof sends; the test will show you.
Your Airtable plan sets run limits
Airtable says the trigger is on all its plans with varying limitations, and each run counts toward the workspace limit.
Read from Airtable’s docs
These Airtable steps follow Airtable’s support article as of 2026-11-17 and were not clicked through in a live base.
FAQ
Questions people ask
Short answers to what usually comes up next.
Do I need Zapier or Make for Airtable?
Possibly not. Airtable can receive a webhook itself. You need a middleware only if its trigger will not accept the request StoryProof sends, which the test will reveal.
Can records update when a review is approved later?
This page covers creating a record when a review arrives. Changing it on approval is not described here, so update the status field by hand.
Can video reviews go into an attachment field?
Only if the delivery carries something Airtable can attach, which you will see in the test. Otherwise store a link back to the review.
Is the webhook URL safe to share with a freelancer?
Share it as little as possible. Anyone holding it can create records in your base.
Still have a question? Ask the StoryProof team or book a demo.
Plan campaigns with the proof already in the base
Collect reviews with StoryProof and have each new one become an Airtable record on arrival.
Sources
- Airtable automation trigger: When webhook received, Airtable Support. Checked 2026-11-17.
Last updated 2026-11-17.