Overview
Act on new reviews the moment they arrive, in the tools your team already uses. Reviews webhooks send real-time review data to external systems such as email platforms (ESPs), CRMs or analytics tools, even when they don't have a direct integration with Okendo.
Before you begin
đ Webhooks are available on the Advanced plan and above. View pricing.
New to webhooks? Read Getting started with webhooks and Okendo first.
Use cases for Reviews webhooks
Here are a few examples of what merchants use webhooks for:
Send review data to your email marketing platform to segment customers based on the data or follow up with them when a review is submitted.
Notify teams when reviews are created to moderate based on the content and helpful ratings.
Push review data to CRMs or customer profiles to support your retention or support teams.
Events that can be subscribed to
You can configure webhooks to notify your system when a review is:
Created - The most common use case whenever a review is submitted.
Updated - When an existing review is updated with information.
Deleted - When a review is deleted from the database - typically initiated by Okendo for specific cases.
Data included in each event
Review details
Review ID
Subscriber ID
Product ID
Variant ID
Review content
Title
Body
Rating
Sentiment
Whether the product is recommended
Whether the review contains profanity
Date created
Product attributes
Reviewer info
Name
Email
Verified status
Social connection
Location
Avatar URL
Reviewer attributes
Attached media info
Review reply
Reply body
Date created
Whether it is private
Reward or incentive offered (if applicable)
Review status
Helpful & Unhelpful count
Tags applied
How to subscribe to Reviews webhooks
Webhook setup requires some developer support. Your team will need to:
Set up an endpoint to receive review data in your desired platform or use a middleware such as Zapier.
Subscribe to webhook events through the Okendo API using the likes of Postman or through code.
Test and verify that the events are being sent and received correctly.
Refer to our technical documentation for the full setup details:
