Webhook security
Secure Your Inbound Testimonial Webhooks
An automation URL that starts review requests is a door into your customer email. Anyone who can call it with the right details can make StoryProof email whoever they name. The protections exist: a secret token on every request, an optional HMAC signature check, and a list of event names the automation will accept. This page is about using them well and spotting trouble early.
- Where the token should and should not live
- When the HMAC check is worth switching on
- A monthly look at what actually arrived
The problem, solved
The worries, and the controls that answer them
Every fix uses a control StoryProof says the inbound webhook has. Names of headers and the signing method are shown in the automation’s settings, not here.
Situation 1 of 6
Our webhook URL is in a shared doc
Setup notes, screenshots and chat threads travel further than anyone intends.
How StoryProof solves it
From Pro, requests carry a secret token as well as the URL. Keep that token only in the calling tool’s secret or credential field, never in notes.
Situation 2 of 6
Could someone forge a call to it?
A token proves the caller knew a secret once. It says nothing about whether the body was changed on the way.
How StoryProof solves it
Switch on the optional HMAC signature check when the calling tool or your own code can sign requests the way the automation’s settings describe.
Situation 3 of 6
The CRM sends every event to the URL
A tool set to post all activity can start requests on events that have nothing to do with a finished job.
How StoryProof solves it
Limit runs to the event names you expect, so anything else is not run.
Situation 4 of 6
We would not notice misuse
Forged or runaway calls look like normal activity unless someone reads what arrived.
How StoryProof solves it
Logs list every webhook that arrived and every run, with the reason it ended. Read them on a schedule; they are kept for 30 days.
Situation 5 of 6
A flood could email the same people
If a bad call does get through, the worst outcome is customers being asked again and again.
How StoryProof solves it
Use a review request step that skips anyone who has already reviewed or was asked recently, which limits the damage a repeat call can do.
Situation 6 of 6
Too many people can edit automations
Everyone who can open the automation’s settings can copy its token.
How StoryProof solves it
Roles and permissions, on every plan, give each teammate only the parts of the workspace they need.
Security review
Review one inbound webhook in fifteen minutes
Do this for each automation that starts from a webhook. Repeat it when the calling tool, its owner or the automation changes.
Ticks stay in your browser. Nothing about your webhook is sent anywhere.
One automation, before and after the review
Set up in a hurry
- URL and token pasted in a team wiki for convenience
- Every CRM event posted to the automation
- HMAC left off because nobody looked
- No one has opened the log since launch
Reviewed
- Token kept in the calling tool’s credential field only
- Only the expected event names start a run
- Signature check on where the caller can sign
- Monthly log read with a named owner
In StoryProof
Tighten an existing webhook without breaking it
- 1
List what calls it
Open the log and note every source and event name that arrived in the last weeks. That list is what you will allow.
- 2
Restrict the event names
In the automation’s settings, limit runs to the event names from your list.
- 3
Move the token somewhere private
Put it in the calling tool’s secret field and delete copies from notes and tickets.
- 4
Turn on HMAC where possible
If the caller can sign as the settings describe, enable the check and send one test on your own contact. Tests run every step for real.
- 5
Add a heads-up
Optionally add a step that sends an in-dashboard notification or emails up to ten teammates when this automation runs.
What happens next: Re-run the security review whenever the calling tool or its owner changes.
Before you start
Honest limits
No header names or algorithm here
StoryProof states there is a secret token and an optional HMAC check. The exact headers and signing method are in the automation’s settings; this page does not guess them.
Some callers cannot sign
Many no-code tools can send a fixed header but cannot compute a signature. For those, the token and event name limit are your controls.
Logs only go back 30 days
Older arrivals are not kept, so a review done every few months will miss part of the picture.
Not a security audit
This is a practical checklist for one automation, not a review of your wider systems or a compliance assessment.
FAQ
Questions people ask
Short answers to what usually comes up next.
Is the URL alone enough to start a run?
StoryProof says requests carry a secret token as well, so treat the URL and token as one secret and keep both private.
Which HMAC algorithm and header does StoryProof use?
This page does not state them on purpose. Read them in the automation’s settings and configure your caller to match.
What does limiting event names protect against?
A tool that posts every kind of event, or a stray call, will not start the automation unless its event name is on your list.
How do I spot misuse?
Read the automation log, which shows every webhook that arrived and why each run ended, and add a team alert if you want to hear about every run.
Still have a question? Ask the StoryProof team or book a demo.
Start review requests from your tools, safely
Every automation gets its own URL, a secret token, an optional signature check and event limits.
Last updated 2026-11-18.