Stripe to StoryProof
Start Testimonial Requests from Stripe Payments
Stripe knows the moment someone pays you. StoryProof has no Stripe app, but from Pro every automation has its own inbound webhook URL. Put Zapier or Make between the two and a completed payment can start a delayed, polite testimonial request.
- Pick the Stripe event that means the customer really paid
- Send the payer email and name on to the automation
- Wait long enough for the purchase to be used first
Setup checklist
Wire one Stripe payment to one testimonial request
Tick each item as you build. The Stripe and Zapier items come from their own documentation; the StoryProof items come from the product.
Ticks stay in your browser and are not saved.
The problem, solved
What goes wrong between a payment and an ask
- Problem 1
There is no StoryProof app in Stripe
Stripe’s app marketplace will not list StoryProof, so the obvious route seems closed.
How StoryProof solves it
From Pro, each automation has a secure URL another tool can call. A Zapier or Make step that runs on a Stripe payment calls it.
- Problem 2
The ask arrives before the parcel does
A request sent seconds after checkout asks for a verdict on something the buyer has not touched.
How StoryProof solves it
Put a wait of days or weeks after the webhook trigger, or wait until a set weekday and time, before the request step runs.
- Problem 3
Repeat buyers get asked every time
A loyal customer who pays monthly would hear from you twelve times a year.
How StoryProof solves it
The review request action skips anyone who has already reviewed or was asked recently, so a second payment does not mean a second ask.
- Problem 4
Night purchases trigger night emails
A sale at 2am in one timezone should not mean an email at 2am in the buyer’s.
How StoryProof solves it
Limit sending to working hours, skip weekends and use each recipient’s timezone in the automation settings.
- Problem 5
We cannot tell whether Zapier reached StoryProof
When no request goes out, you need to know which side dropped it.
How StoryProof solves it
The automation log lists every webhook that arrived and why each run ended, for 30 days.
Which Stripe trigger fits how you sell
All four are Zapier triggers for Stripe. The descriptions are Zapier’s; the advice column is ours.
In StoryProof
From a paid charge to a sent request
Step 1 of 4
Create the automation and copy its URL
Start a new automation from the inbound webhook trigger. Note the URL and the secret token shown in its settings.
Step 2 of 4
Add the wait, then the request
Decide how long a buyer needs before they can judge the purchase, set that as a wait, then add the review request step.
Step 3 of 4
Build the Zap or scenario
Trigger on the Stripe event you chose, then POST to the automation URL with the payer email and name as JSON.
Step 4 of 4
Pay yourself and read the log
Use your own email for a real test payment. Check the automation log shows the webhook and the waiting run before you publish.
Before you start
Before you rely on it
No direct Stripe connection
StoryProof does not read Stripe. Every run starts because Zapier or Make called the automation webhook.
Field names come from your sample
This page does not list Stripe’s payload or StoryProof’s field names. The sample event you paste shows them.
Requests are email
The ask goes by email only, so a payment with no email address cannot start a useful run.
Two plans, two bills
Automations need StoryProof Pro or above, and Zapier lists its webhook action as unavailable on its Free plan.
Written from vendor docs
The Stripe trigger names and the Zapier and Make settings follow their documentation as of 2026-11-18 and were not clicked through in a live account.
FAQ
Questions people ask
Short answers to what usually comes up next.
Can I point a Stripe webhook endpoint straight at StoryProof?
This page does not cover it. Stripe endpoints send Stripe’s full event in its own format, which was not tested against the automation. A Zapier or Make step lets you choose exactly which fields and headers go out.
What happens if the customer asks for a refund during the wait?
A later refund does not undo a run that already started. Shorter waits reduce the chance, and the automation log shows which runs are still waiting.
How long should the wait be?
Long enough for the buyer to have used what they paid for. A download can be judged in days; a course or a service often needs weeks.
What does the customer receive?
One email with your collection link, where they can record a video, leave an audio note or write a review in the browser.
Can I try this before paying for anything?
Every account starts with a free trial and no credit card. Check that the trial includes automations before you build the Zap.
Still have a question? Ask the StoryProof team or book a demo.
Turn paid customers into testimonials
Build the automation in StoryProof, then let each Stripe payment start it.
Sources
- Stripe integrations, Zapier. Checked 2026-11-18.
- Send webhooks in Zaps, Zapier Help Center. Checked 2026-11-18.
- HTTP app, Make. Checked 2026-11-18.
Last updated 2026-11-18.