What are customers saying about our products in their Yotpo reviews?
Yotpo connects Memtro to your store's reviews. It reads product and site reviews with score, title, text, SKU, sentiment and dates, the products Yotpo knows with price and status, and star-rating summaries per product. Reviews lag about an hour, and a reviewer's email is never returned. When asked, and once an administrator has granted the action by name, it records and updates orders and fulfilments, adds and updates products, creates or updates customers and submits a review a reviewer gave you. Review-request emails stay suppressed unless you ask, and a submitted review emails the reviewer a verification request.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Yotpo tool, reads what it needs, and answers with the source cited.
These tools change something in Yotpo. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Yotpo for you. Each event can start a job, with the event as its input. Yotpo signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Yotpo is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Yotpo + MemtroWhat are customers complaining about in Yotpo reviews this week?
Show me the low-scoring reviews posted since Monday
Which products have the lowest average star rating?
What is the average score of reviews from verified buyers this month?
Mark the Classic Travel Mug as discontinued in Yotpo
Maya Okafor, head of customer experience at Acme Ltd, asked what customers complained about in Yotpo reviews this week. Memtro pulled the low-scoring reviews, grouped them by SKU and showed that most mentioned a loose lid on one travel mug.
Tom Reilly, ecommerce manager at Northwind, asked Memtro to mark the old travel mug as discontinued now its replacement had launched. Memtro updated the product in Yotpo's catalogue, and Yotpo stopped sending review requests and showing widgets for it.
The teams that lean on Yotpo most, a question each of them asks, and what they connect beside it.
A record in Yotpo is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In the Yotpo admin, open Account Settings → General Settings and copy the Store ID from the bottom of the page.
On the same page choose Get secret key, enter the verification code Yotpo emails you and copy the secret. Only an account administrator can see it, and it grants the whole store's API, so keep it to this connection.
In Memtro, open Connections → Yotpo and paste the Store ID (app key) and the API secret.
Ask your first question: what are customers complaining about in Yotpo reviews this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Yotpo tools are the same everywhere.
Only when you ask, and only what it has been granted: record an order in Yotpo, with its automatic review-request email suppressed unless asked; update or cancel a recorded order; add a fulfilment to an order, which makes it eligible for a review request; add a product to Yotpo's catalogue; update a product's details in Yotpo; create or update a customer by external id or email; submit a review on a reviewer's behalf, which emails them a verification request. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Store ID and API secret. In the Yotpo admin, open Account Settings → General Settings and copy the Store ID from the bottom of the page.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Yotpo for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
