Make to StoryProof
Start Review Requests From Make Scenarios
Make (formerly Integromat) already watches the tools where customers finish things: a form, a shop, a spreadsheet, a CRM. Add one HTTP module at the end of that scenario and it can call a StoryProof automation’s own URL, from Pro, which then sends the testimonial request. This guide is about that outbound call from Make, not about catching StoryProof reviews inside Make.
- Make a request, set to POST with a JSON body
- Data structure or JSON string, and why it matters
- Stop the scenario when StoryProof answers with an error
Module checklist
Configure the HTTP module that calls StoryProof
Work through it with the Make scenario open in one tab and the StoryProof automation in another.
Your ticks are stored in this browser only.
The problem, solved
Where a Make to StoryProof call usually breaks
- Problem 1
We set up the wrong Make webhook
Make’s Custom webhook module waits for data to come in. Starting a request needs Make to send data out.
How StoryProof solves it
Call the automation’s own URL with the HTTP module. From Pro, every automation has one that a Make step can call to start review requests.
- Problem 2
A name with an apostrophe broke the JSON
Typing JSON by hand into the string option means every quote in a customer’s name is yours to escape.
How StoryProof solves it
Use Make’s Data structure input, then paste the run’s sample event into StoryProof and confirm it found the email and name.
- Problem 3
The scenario runs every time a row changes
A sheet or CRM watch can send the same customer several times in a week.
How StoryProof solves it
The review request step can skip anyone who has already reviewed or was asked recently, so duplicates do not become duplicate emails.
- Problem 4
We cannot see which customers came from Make
Later, nobody knows why a contact received a request.
How StoryProof solves it
Add a step in the automation that tags the contact or adds it to a Smart List, so its origin is visible in StoryProof.
- Problem 5
Make shows success but nothing was sent
A green tick in Make only means StoryProof answered. What happened next is on the other side.
How StoryProof solves it
StoryProof’s automation logs show each webhook that arrived and the reason a run ended, kept for 30 days.
Make a request settings that matter for this call
In StoryProof
Four steps from scenario to sent request
Step 1 of 4
Build the StoryProof side
Start an automation from its inbound webhook, add the review request with skip rules, and keep it in draft.
Step 2 of 4
Add HTTP Make a request
POST to the StoryProof URL, JSON body as a data structure, email and first name mapped, token placed as StoryProof asks.
Step 3 of 4
Run once on your own email
Paste the sample event into StoryProof, check the chosen fields, then run a test on your contact. It sends for real.
Step 4 of 4
Publish and schedule
Publish the automation, switch the scenario on and read both histories after the first day.
Before you start
What to know before relying on it
No StoryProof app in Make
Nothing here is a listed Make app. The connection is Make’s generic HTTP module calling an automation’s URL.
Email is the only channel
StoryProof sends review requests by email and does not send SMS, whatever other modules your scenario has.
Make’s own plan terms apply
Scenario runs are governed by your Make plan, not by StoryProof. This page does not estimate that usage or its cost.
Payload is yours to define
No field names are prescribed here. The sample event you paste shows what StoryProof picked as email and name.
Based on Make’s help
The Make settings follow its help center as of 2026-11-18 and were not tried in a live scenario.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is this the same as the Make page about testimonial webhooks?
No. That page catches new StoryProof reviews in Make. This one has Make call StoryProof so a review request starts.
Can I still use Integromat instructions?
Make is the current name of the tool once called Integromat. Use Make’s current help pages, since module names and settings have changed over time.
Should Make wait before calling StoryProof?
It does not need to. Put the wait in the StoryProof automation, where waits run from minutes to weeks, and keep the scenario fast.
What happens if StoryProof rejects the call?
With Return error if HTTP request fails set to Yes, Make stops the run and shows the error, so you can fix the URL, token or event name.
Still have a question? Ask the StoryProof team or book a demo.
Let any Make scenario ask for a testimonial
Create an automation, copy its URL into one HTTP module and the rest happens in StoryProof.