Zapier rollout
Connect Testimonial Webhooks to Zapier
There is no StoryProof app in Zapier’s directory to pick from. What exists is a webhook, from Pro, and Zapier’s own Webhooks by Zapier trigger that catches it. Set that up once and every new review can feed any app Zapier connects to.
- Catch Hook, chosen over Catch Raw Hook for most Zaps
- A dated week from first test to switched on
- Zap history checks after launch
Rollout plan
A week from first catch to a Zap you trust
Pick the day you start. The plan spaces out testing so a broken step shows up before your team depends on it.
Day 0
Create the trigger
New Zap, trigger Webhooks by Zapier, event Catch Hook. Copy the URL from the Test tab.
Day 0
Connect StoryProof and send a review
Paste the URL where your StoryProof settings list webhooks, leave one review through your own link, then click Test trigger in Zapier.
Day +1
Build the actions
Add the steps that use the review, mapping only fields that appeared in the test. Add a filter step if only some reviews should continue.
Day +2
Second test, then publish
Leave another review with different content, check every step handles it, and publish the Zap.
Day +7
Read Zap history
Compare the week’s runs with the reviews StoryProof received. Any gap is worth chasing now.
Day +30
Monthly check
Confirm the Zap owner still has access and that task usage is where you expected.
Dates are calculated in your browser. Nothing is saved.
The problem, solved
The reasons a StoryProof Zap stalls
- Problem 1
There is no StoryProof app in Zapier
Searching the app directory turns up nothing, and many people stop there.
How StoryProof solves it
Use the webhook instead. From Pro, every new review is sent to the URL you give it, and Webhooks by Zapier catches it.
- Problem 2
Zapier says it found no request
The trigger test waits for something new to arrive. A URL pasted after the review was left catches nothing.
How StoryProof solves it
Add the webhook in StoryProof first, then leave a fresh review, then test. Each new review is sent as it arrives, so timing matters.
- Problem 3
We want Zapier to chase customers who have not replied
Building reminder emails in Zapier means tracking who already responded.
How StoryProof solves it
StoryProof already does this from Pro: follow-ups send a reminder after three days and a last email four days later, and stop as soon as the customer leaves a testimonial.
- Problem 4
A Zap posted a review publicly before approval
The webhook fires on arrival, so a Zap that publishes somewhere public skips your check.
How StoryProof solves it
Keep Zaps internal, or add a human step. Nothing appears on your site until you approve it in StoryProof.
- Problem 5
We are on a plan without webhooks
Zapier cannot catch what is not sent.
How StoryProof solves it
On every plan, the app shows an alert when a review lands, so someone can act by hand until webhooks are available.
Catch Hook or Catch Raw Hook
Both are Webhooks by Zapier triggers. Zapier recommends Catch Hook for most cases.
In StoryProof
The short version
Step 1 of 4
Add a Catch Hook trigger
Choose Webhooks by Zapier, event Catch Hook, and copy the URL shown in the Test tab.
Step 2 of 4
Register it in StoryProof
Paste the URL where your StoryProof settings list webhooks.
Step 3 of 4
Leave a review and test the trigger
Use your own collection link, then click Test trigger. Inspect every field Zapier received.
Step 4 of 4
Add actions and publish
Map the received fields into the apps you need, test again with a second review, and publish.
Before you start
What Zapier will not fix
No StoryProof Zapier app
StoryProof is not described as having an app in Zapier. The webhook and Zapier’s generic trigger are the link.
The fields are yours to discover
This page does not list the webhook’s contents or event names. The test trigger shows them.
Two plans involved
StoryProof includes webhooks from Pro, and Zapier lists its webhook trigger as unavailable on its Free plan.
Written from Zapier’s help
The Zapier steps follow its help center as of 2026-11-17 and were not clicked through in a live account.
FAQ
Questions people ask
Short answers to what usually comes up next.
Why is there no StoryProof trigger to choose in Zapier?
StoryProof is not listed as a Zapier app. Its webhook works with Zapier’s general Webhooks by Zapier trigger instead.
Do I need Catch Raw Hook to verify anything?
Only if you have a specific reason to read the raw request or headers. Most Zaps use Catch Hook.
How many tasks will this use?
That depends on your Zapier plan and how many steps each run takes. Zap history shows real usage after the first week.
Can a Zap send the review request emails too?
You do not need it to. StoryProof sends requests by email and, on plans with automations, handles follow-ups itself.
Still have a question? Ask the StoryProof team or book a demo.
Start a Zap with every new review
Collect reviews with StoryProof and catch each one in Zapier through a webhook.