Before the renewal call
The account lead asks how active BigCo is before their renewal. Memtro reads the Pendo account: first visit in March last year, last visit yesterday, plan Growth, and two NPS responses from the last 30 days, both promoters.
Ask when an account last used the product, and what its users said in Pendo surveys.
Connect Pendo with an integration key and Memtro reads tagged pages and features, in-app guides, one visitor or account with first and last visit and metadata, shared segments, saved reports and survey and NPS responses. It reads on demand and there is no hourly sync. With a write-enabled key, and once an administrator has granted the action by name, it can publish, stage or switch off guides and change who they target, which users see at once, manage segments and Listen feedback, and permanently erase named visitors' data. Deleted segments, feedback and visitors cannot be restored.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Pendo tool, reads what it needs, and answers with the source cited.
These tools change something in Pendo. 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, then add the address it shows as a webhook in Pendo, choosing the same kinds; the tab shows Pendo's own steps. Each event can start a job, with the event as its input. Pendo signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Pendo 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.
When did the Northwind account last visit the product?
Which in-app guides are still in draft?
What did detractors say in last month's NPS survey?
When was priya.nair@acme.example first and last seen in Pendo?
Switch off the old billing guide and publish the new one to the Enterprise segment
The account lead asks how active BigCo is before their renewal. Memtro reads the Pendo account: first visit in March last year, last visit yesterday, plan Growth, and two NPS responses from the last 30 days, both promoters.
Product manager Sofia Marsh asks Memtro to replace the old billing walkthrough. Memtro disables the old guide, points the new one at the Enterprise accounts segment and sets it public, and those users see the new guide in the product straight away. Nobody is emailed.
The teams that lean on Pendo most, a question each of them asks, and what they connect beside it.
A record in Pendo 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.
Pendo API access depends on your subscription's level of service: integration keys exist only where it is enabled
As an admin open Settings → Integrations → Integration Keys, add a key with a description, and tick Allow Write Access only if Memtro should change guides, feedback or segments when asked. Unticked, it only reads. Create it and copy it: it is shown once
In Memtro open Connections → Pendo, paste the Integration key, set Region host to the host you sign in on (app.pendo.io for US, app.eu.pendo.io for EU, or your region's), and connect
Ask when Northwind last used the product
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Pendo tools are the same everywhere.
Only when you ask, and only what it has been granted: publish, stage, disable or return to draft an in-app guide (changes what users see in the product); change which segment an in-app guide targets; let one visitor see a guide again (erases their seen record for it); log a feedback request in Pendo Listen for an account; edit a Listen feedback request; delete up to ten Listen feedback requests (permanent); create a shared segment from a list of visitor or account ids; rename an API-made segment or replace its visitor list; add or remove visitors in an API-made segment; delete a segment (permanent); erase named visitors and their data from Pendo (GDPR/CCPA, permanent). 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.
Integration key. Pendo API access depends on your subscription's level of service: integration keys exist only where it is enabled.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Pendo, choosing the same kinds; the tab shows Pendo's own steps. 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