Overview · 1:54
See an approved testimonial reach your team.
Follow an approval from a signed webhook to your own notification workflow, then see how delivery inspection and replay keep you in control.
8 chapters · Captions · Full transcript
Read the transcript
Customer proof. Connected.
A great customer story just got approved. Now put it in front of the team who can use it.
Choose what starts your workflow
With ReTestimonial’s outbound webhooks, testimonial events can start your next workflow. Open Developer settings, add your endpoint, and choose the events you need. Here, we’ll send approved testimonials to a team notification workflow.
Make the connection
Create the endpoint, securely save its signing secret, and configure your receiver to verify incoming requests. Send a test to check the connection.
An approval becomes an action
When Sienna’s testimonial is approved, ReTestimonial queues the event and sends a signed request. Your configured workflow can turn those details into a useful team notification, with the customer’s story ready to read.
See what reached the receiver
Open the delivery log to inspect the event, payload, and response. Signed requests help your receiver verify the source, while a stable delivery ID supports duplicate protection.
Give delivery another chance
If the receiver is unavailable, automatic retries give it another chance. ReTestimonial makes up to four attempts, with increasing delays, and keeps the result visible in your delivery log.
Recover. Pause. Resume.
After fixing the receiver, replay the failed delivery from the dashboard. You can also pause deliveries while you work. Subscribed events keep queuing, ready to send when you activate the endpoint again.
Put customer proof into motion.
Put your customer proof into motion. Start free with ReTestimonial. Connect your workflow with Outbound Webhooks on Premium or Business.
Six events. One predictable shape.
Subscribe to the lifecycle moments that matter. Every event ships with a stable JSON envelope versioned 2026-02-01, a content snapshot, and a normalized source category.
A new testimonial — text, video, or audio — landed via form, manual entry, import, review-platform sync, or extension. Source category included.
A testimonial transitioned to APPROVED. Fires from the dashboard, bulk actions, or auto-approval on insert.
Non-status edits to copy, ratings, custom fields, tags, or attribution. Status transitions fire their own typed events.
Archived or rejected via the dashboard or bulk action. Fires once, replaces a generic update event.
Marked as spam by moderation, bulk action, or detection. Use it to sync downstream lists or alert humans.
Hard-deleted with a typed reason — manual_delete, bulk_delete, source_bulk_delete, import_rollback, spam_cleanup.
HMAC-SHA256. No exceptions.
Every payload ships with an X-RT-Signature header. Verify it in three lines, reject anything that doesn’t match. Replay attacks die at your edge.
Your endpoint hiccups. We keep dispatching.
Four attempts over an hour, exponential backoff, durable outbox. If you 5xx, we come back. If you 4xx, we stop and tell you. Either way, no event is silently dropped.
A predictable envelope. Always.
The same eight top-level keys for every event, every endpoint, every project. Build your handler once and trust the shape forever.
Anywhere that speaks HTTPS.
Everything an integrator actually needs.
Built for engineers who’ve read the postmortem.
Durable outbox, idempotent IDs, signed payloads, replayable history. The features you wish every webhook product shipped with.
| Plan | Premium 1 endpoint · Business 5 endpoints |
| Signing | HMAC-SHA256, X-Signature: t=…,v1=… |
| Delivery semantic | At-least-once · Idempotency-Key per attempt |
| Retry schedule | 60s · 10m · 1h · max 4 attempts |
| Timeout | 10s per attempt |
| TLS | HTTPS required · redirects blocked |
| Auto-disable | 15 consecutive failures · owner email |
| Audit log | Succeeded 30d · Failed/Canceled 90d |
| Security | Signed delivery · SSRF protection · published security documentation |