Testimonials as content entries
Push New Testimonials Into Your CMS
Some teams want each testimonial to exist as an entry in their CMS, with its own fields, so templates, search and editors can use it like any other content. StoryProof can send every new review to your own tools by webhook. A middleware step can turn that into a draft entry, and WordPress is the worked example here because its REST API is public and stable. The entry stays a draft until an editor publishes it.
- Every new review becomes a draft entry
- WordPress REST API as the worked example
- An editor publishes, never the webhook
Setup checklist
From new review to draft entry
Follow it top to bottom. The WordPress items come from the WordPress developer docs and the middleware items from Make’s webhooks help, both read on 2026-11-17. Another CMS needs its own create entry call in place of the WordPress one.
Ticks stay in your browser. Nothing is saved or sent.
The problem, solved
Problems this flow is built around
- Problem 1
Editors retype every quote into the CMS
Copying by hand is slow, introduces typos and means the CMS lags weeks behind what customers have said.
How StoryProof solves it
From Pro, webhooks send every new review straight to your own tools as it arrives, ready for a middleware step to write into the CMS.
- Problem 2
A review went public before approval
The webhook sends reviews as they arrive, which is before anyone has checked them. Auto publishing would skip moderation entirely.
How StoryProof solves it
In StoryProof nothing goes public until approved. Mirror that in the CMS by creating drafts only, and publish once the testimonial is approved.
- Problem 3
Which fields does the webhook send?
Guessing field names leads to empty titles and broken entries that nobody notices until a template renders them.
How StoryProof solves it
This page does not list payload fields. Send one test review, read the real delivery in your middleware, and map only what is there.
- Problem 4
Too many people can approve reviews
If the CMS editor and the StoryProof approver are different people, both need to know who signs off first.
How StoryProof solves it
Roles and permissions, on every plan, give each teammate only the parts of the workspace they need, so approval sits with the right person.
- Problem 5
Do we even need entries?
If the only goal is showing testimonials on pages, a CMS sync adds moving parts you will have to maintain.
How StoryProof solves it
A widget is two lines of HTML and shows only the approved testimonials you choose. Use entries when templates or search need the text as content.
In StoryProof
Build it in four moves
Step 1 of 4
Point the webhook at your middleware
Create the receiving webhook in Make, Zapier or your own code and add its URL where StoryProof lists webhooks.
Step 2 of 4
Look at a real delivery
Submit one test review, open the received data and note which values you can map. Do not build from a guessed structure.
Step 3 of 4
Create a draft entry
Add an HTTP step that posts to your CMS’s create endpoint with the integration user’s Application Password and status set to draft.
Step 4 of 4
Publish after approval
An editor approves the testimonial in StoryProof, then publishes its CMS draft. Both stay private until then.
Before you start
Limits of a webhook sync
One way, new reviews only
The webhook sends new reviews as they arrive. Nothing on this page updates or deletes a CMS entry when something changes in StoryProof.
No native CMS integration
StoryProof is not claimed to connect to WordPress or any CMS directly. The middleware or your own endpoint does the writing.
Payload format not documented here
Field names, events, retries and signatures are not described. Build from a test delivery and recheck it after changes.
WordPress steps as of 2026-11-17
The REST API and authentication details follow the WordPress developer docs as read on 2026-11-17. They have not been run on a live site by us.
Security of the credentials
The Application Password can create content. Store it only in the middleware’s secure settings and revoke it if the integration is retired.
FAQ
Questions people ask
Short answers to what usually comes up next.
Why drafts and not published posts?
Because the webhook fires when a review arrives, before anyone approves it. Publishing straight away would put unreviewed text on your site.
Does this work for Contentful, Sanity or Strapi?
The pattern does. Swap the WordPress call for that CMS’s create entry API, following its own docs, and keep entries unpublished.
Can a video testimonial become an entry?
Only if the test delivery gives you something usable for it, such as a link. Check the real delivery before planning a video field.
Is a widget simpler?
Usually. If you only need testimonials on pages, embed a widget and choose its testimonials in StoryProof. Use entries when your templates need the text itself.
Still have a question? Ask the StoryProof team or book a demo.
Feed your CMS from real customer words
Collect testimonials in StoryProof and send each new one to your own stack as it arrives.
Sources
- REST API Handbook: Posts (Create a Post), WordPress.org. Checked 2026-11-17.
- REST API Handbook: Authentication (Application Passwords), WordPress.org. Checked 2026-11-17.
- Webhooks, Make. Checked 2026-11-17.
Last updated 2026-11-17.