Skip to main content

A person to tell, or a system to feed

Notifications or Webhooks for New Testimonials

There are two ways to find out that a testimonial has arrived. The in-app alert, on every plan, tells whoever opens StoryProof. A webhook, from a paid plan, sends each new review to a tool you own the moment it lands, where it can post to a channel, add a spreadsheet row or start some other job. They solve different problems. Five questions below tell you which you need, or whether you need both.

  • Who has to act, and where they spend the day
  • Whether a middleware or a developer is available
  • No invented payloads: test with one real review

Decision helper

Alert, webhook, or both?

Answer for the people who need to know about a new testimonial, not for the tool you already like.

Who needs to know when a testimonial arrives?
Where should the news show up?
Who could set up and maintain a webhook?
Are you on Pro or above, or willing to be?
Does someone still need to read and approve each testimonial in StoryProof?

Your answers stay in this browser tab and are not sent anywhere.

The problem, solved

What each option fixes, in StoryProof terms

  • Problem 1

    I just want to know it arrived

    A webhook is overkill when the only person who cares opens the app every day anyway.

  • Problem 2

    The team never opens StoryProof

    Sales, support and leadership would love to see new praise, but they will not log in to look for it.

  • Problem 3

    Will a webhook publish things?

    Some worry that sending a review elsewhere means it is suddenly public.

  • Problem 4

    Only bad reviews need speed

    If urgency is about low ratings, a general webhook can be more than you need.

  • Problem 5

    People want in just to watch

    Giving everyone a seat so they can see new testimonials uses seats and widens access.

In-app alert and webhook compared

QuestionIn-app alertWebhook
PlanEvery planFrom Pro
Who sees itPeople in the StoryProof appWhatever tool receives it
EventsReview lands, import finishes, someone joinsEvery new review
SetupNoneA receiving URL in a middleware tool or your own endpoint
UpkeepA person who checks the appSomeone who owns the receiving side when it breaks

In StoryProof

Act on the decision

Middleware steps follow Zapier’s and Make’s own help pages. The shape of what StoryProof sends is not described here: find it by testing.

  1. 1

    Alerts: give them an owner

    Name the person who checks in-app alerts each day and what they do with a new review.

  2. 2

    Webhook: create the receiving URL first

    In Zapier, a Webhooks by Zapier trigger with Catch Hook gives you a unique URL (Zapier’s docs say this needs a Professional, Team or Enterprise plan). In Make, a custom webhook module gives you one. Or your developer exposes an endpoint.

  3. 3

    Paste that URL where the app lists webhooks

    Add the receiving URL in your StoryProof settings, where the app lists webhooks.

  4. 4

    Send one test review and inspect it

    Submit a test testimonial yourself, then look at the delivery your receiver recorded. Zapier tests a webhook trigger once a real event has arrived; Make suggests sending sample data to learn the structure. Build only on the fields you actually see.

  5. 5

    Decide what happens downstream

    Post to a channel, add a row, open a task. Keep approval in StoryProof either way.

What happens next: Leave the test testimonial unapproved so it never appears anywhere public, and tag it as a test so nobody approves it by mistake.

Before you start

Limits worth knowing before you choose

What this does not cover, and what to check on your side. Better to know now than after launch.

  1. 01

    No payload is documented here

    This page does not describe field names, events, retries or signing for the StoryProof webhook. Inspect a real delivery before building on it.

  2. 02

    No native chat apps are claimed

    There is no claimed StoryProof app for Slack, Teams, Zapier or Make. The webhook is the link, and the receiving tool does the rest.

  3. 03

    Middleware has its own plans

    Zapier’s docs say Webhooks by Zapier is not on its Free plan. Check the current plan of whichever tool receives the webhook.

  4. 04

    Vendor steps are as of 2026-11-17

    The Zapier and Make steps follow their help pages on that date and have not been tried on a live account for this page.

  5. 05

    Alerts stay in the app

    The in-app alert is shown in StoryProof. This page does not claim email or phone delivery of every review.

FAQ

Questions people ask

Short answers to what usually comes up next.

Do I need a paid plan for notifications?

No. In-app alerts are on every plan. Webhooks start on Pro.

What data does the webhook send?

This page does not say, on purpose. Send one test review to your receiver and read what actually arrives before mapping any fields.

Can I post new testimonials to Slack?

Through the webhook, yes, by pointing it at a tool that can post to Slack. No native StoryProof Slack app is claimed.

Is a webhook more secure than giving people a seat?

They are different trade offs. A webhook copies review data into another tool, so whoever can see that tool can see the reviews. Choose the receiving place with that in mind.

Can I use both?

Yes. Many teams keep the in-app alert for approvers and use a webhook to tell everyone else.

Still have a question? Ask the StoryProof team or book a demo.

Start with the alerts, add a webhook when you need it

In-app alerts come with every StoryProof plan. Webhooks are there when the rest of the team needs the news.

Sources

  1. Trigger Zap workflows from webhooks, Zapier. Checked 2026-11-17.
  2. Webhooks, Make. Checked 2026-11-17.

Last updated 2026-11-17.