What are people saying in our surveys this week?
Survicate connects Memtro to your survey feedback. It reads your surveys first, with type, whether enabled, response counts and launch dates. For one survey it reads the questions with their answer choices, and when the first and last responses came in. It then reads responses with answers labelled by question: chosen options, ratings, NPS groups and comments, with NPS counts over what was returned. The connector reads and nothing else. Who responded is never returned. The key needs a paid plan that includes API access, and only organisation owners and workspace admins can find it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Survicate tool, reads what it needs, and answers with the source cited.
Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Survicate, choosing the same kinds; the tab shows Survicate's own steps. Each event can start a job, with the event as its input. Survicate signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Survicate 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.
What are people saying in the onboarding NPS this week?
Which surveys are enabled right now, and how many responses has each had?
What questions does the pricing page survey ask?
How many detractors did the in-product NPS get since Monday?
Show me the comments from last month's churn survey.
Priya Sharma, head of customer success at Acme Ltd, asked what new customers said in the onboarding NPS this week. Memtro read the week's responses, gave the promoter, passive and detractor counts, and quoted the detractor comments by question.
Dan Fletcher, product manager at Northwind, asked whether the in-product survey launched on Monday was getting answers. Memtro found it in the survey list and gave its response count and when the last response came in.
The teams that lean on Survicate most, a question each of them asks, and what they connect beside it.
A record in Survicate 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.
Freshdesk
Gorgias
Crisp
Groove
Plain
Freshchat
Freshservice
Kustomer
Dixa
HelpCrunch
Custify
Atera
Trengo
ConnectWise PSA
Enchant
Frill
Gladly
HaloPSA
HappyFox
Jitbit Helpdesk
Nicereply
Re:amaze
SolarWinds Service Desk
Stonly
Syncro
Tidio
Teamwork DeskIn the Survicate panel, go to Settings → Organization → Access Keys. Only organisation owners and workspace admins can open that page.
Copy the value in the "API key" row, which is the Data Export key. Do not use the Workspace key or the Secret key on the same page.
In Memtro, open Connections → Survicate and paste the key into API key.
Ask a first question, such as "What are people saying in the onboarding NPS this week?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Survicate tools are the same everywhere.
Not yet. Today every Survicate tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
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. An hourly sync anchors recently changed Survicate records into memory as entities.
API key. In the Survicate panel, go to Settings → Organization → Access Keys. Only organisation owners and workspace admins can open that page.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Survicate, choosing the same kinds; the tab shows Survicate'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