Microsurvey feedback
Maya Okafor, product manager at Northwind, asked what users had said in the pricing microsurvey. Memtro read the answers with the count per button and the comments left, newest first, without naming who gave them.
How many people finished our onboarding tour, and what did the last microsurvey say?
Chameleon shows you your in-product tours and microsurveys with live state and started, completed and exited counts. Memtro also reads microsurvey answers without who gave them, tour interactions by state, segments, tags, environments and pending deliveries. When asked and granted, it can publish or unpublish tours, publish microsurveys, tag them and change their environments. It can show one to a named end user, reschedule or cancel that delivery, and update, clear or delete a user profile. It can also track an event and delete a response or a company. The secret needs a Pro, Growth or Enterprise plan.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Chameleon tool, reads what it needs, and answers with the source cited.
These tools change something in Chameleon. 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 Chameleon, choosing the same kinds; the tab shows Chameleon's own steps. Each event can start a job, with the event as its input. Chameleon signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Chameleon 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.
How many people completed the onboarding tour?
What did people say in the pricing microsurvey this week?
Which tours are live right now?
Which deliveries are still pending?
Unpublish the old billing banner.
Maya Okafor, product manager at Northwind, asked what users had said in the pricing microsurvey. Memtro read the answers with the count per button and the comments left, newest first, without naming who gave them.
At BigCo, a job starts when Chameleon reports that a microsurvey response was finished. It reads the latest answers to that microsurvey and its counts. Tom Reilly, product lead, sees a summary of what people chose and said.
The teams that lean on Chameleon most, a question each of them asks, and what they connect beside it.
A record in Chameleon 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 Chameleon, open Settings → Tokens at app.chameleon.io and generate a new secret token. It is account-wide with no scopes, and needs a plan with Webhooks & APIs.
Open Connections → Chameleon in Memtro and paste the Account secret.
An administrator grants actions such as publish a tour or delete a profile by name to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added in Chameleon's webhook settings.
Ask how many people completed the onboarding tour.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Chameleon tools are the same everywhere.
Only when you ask, and only what it has been granted: publish or unpublish a tour; publish a microsurvey; add or remove a tag on a tour or microsurvey; add or remove an environment on a tour or microsurvey; show a tour or microsurvey to one named end user (create a delivery); reschedule a pending delivery; cancel a pending delivery; create or update an end user's profile properties; track an event for an end user; clear an end user's profile data; permanently delete an end user's profile; delete a microsurvey response; delete a company. 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.
Account secret. In Chameleon, open Settings → Tokens at app.chameleon.io and generate a new secret token. It is account-wide with no scopes, and needs a plan with Webhooks & APIs.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Chameleon, choosing the same kinds; the tab shows Chameleon'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