Ask what customers said in the last Formbricks survey, answer by answer.
Connect Formbricks with an API key and Memtro reads the surveys in the workspaces the key can see, with status and questions, and the responses with each answer beside its question. Answers to address and contact-info questions, and respondents' contact attributes, are never read, and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can create a survey, published at once to anyone with its link if asked, add a response, which runs the survey's webhooks and follow-up emails, overwrite one, and permanently delete a response or a survey.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Formbricks tool, reads what it needs, and answers with the source cited.
These tools change something in Formbricks. 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 Formbricks, choosing the same kinds; the tab shows Formbricks's own steps. Each event can start a job, with the event as its input. Formbricks signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Formbricks 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 did customers say in the onboarding survey this month?
Which surveys are in progress and which are paused?
How many responses has the Acme pricing survey had, and how many finished?
What did people answer to the question about missing features?
Draft a survey asking Northwind users which report they open most
The product lead at Brightwave Ltd asks what customers said in last week's churn survey. Memtro finds the survey, reads its 42 responses with each answer beside its question, and sums up the three reasons that came up most, with quotes.
Dan Fletcher asks Memtro to set up a short survey on which reports Acme users rely on. With the action granted, Memtro creates it as a draft with two choice questions and one open question. Nobody can see or answer it until Dan publishes it in Formbricks.
The teams that lean on Formbricks most, a question each of them asks, and what they connect beside it.
A record in Formbricks 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.
ActiveCampaign
Klaviyo
MailerLite
GetResponse
Instantly
lemlist
Drip
Omnisend
Mailjet
Moosend
Smartlead
Iterable
Dotdigital
Flodesk
LoyaltyLion
Benchmark Email
Braze
Sender
Rewardful
Mailshake
SurveySparrow
RetentlyIn Formbricks open Organization name (top left) → API Keys → Add API Key, add each workspace Memtro should read under Workspace Access with read access, and give write access only if Memtro should add, change or delete responses or surveys when asked
Leave Host blank for Formbricks Cloud (app.formbricks.com), or type your self-hosted server's host name only, a public DNS name with a publicly trusted certificate. Self-hosted installs need Formbricks v4 or later
Paste the API key, shown once, into Connections → Formbricks in Memtro and connect
Ask what customers said in the last survey
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Formbricks tools are the same everywhere.
Only when you ask, and only what it has been granted: add a response to a survey (runs the survey's webhooks, integrations and follow-up emails); overwrite the answers of a response; delete a response permanently; rename a survey; delete a survey permanently; create a survey, as a draft or published at once. 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.
API key. In Formbricks open Organization name (top left) → API Keys → Add API Key, add each workspace Memtro should read under Workspace Access with read access, and give write access only if Memtro should add, change or delete responses or surveys when asked.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Formbricks, choosing the same kinds; the tab shows Formbricks'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