Canvas results
Priya Sharma, lifecycle marketer at BigCo, asked how the onboarding Canvas had done over the past week. Memtro gave its entries, conversions and revenue for the period, with the results of each step.
How has our onboarding Canvas performed this week, and which campaigns are live?
Braze shows you your campaigns and Canvases with status, schedule, channels, tags and message subjects. Memtro reads their results over a period, such as conversions and revenue, plus segments, custom event names, email templates and Content Blocks. When asked and granted, it can create or update an email template or a Content Block. It can send an API-triggered campaign or Canvas to named users. It can also subscribe or unsubscribe them from a subscription group. User profiles are never read, and templates built in the drag-and-drop editor are not returned by the API.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Braze tool, reads what it needs, and answers with the source cited.
These tools change something in Braze. 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.
Once Braze 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 has the onboarding Canvas performed this week?
Which campaigns are enabled and sending email?
What is the subject line of the win-back campaign?
Which custom events can a campaign be triggered on?
Update the footer Content Block with our new address.
Priya Sharma, lifecycle marketer at BigCo, asked how the onboarding Canvas had done over the past week. Memtro gave its entries, conversions and revenue for the period, with the results of each step.
Tom Reilly, CRM manager at Northwind, asked Memtro to fix a typo in the welcome email template's subject. With the action granted, Memtro updated the template and nothing was sent. Messages already built from it kept their own copy.
The teams that lean on Braze most, a question each of them asks, and what they connect beside it.
A record in Braze 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 Braze dashboard, open Settings → APIs and Identifiers → API Keys → Create API Key. Tick the read permissions, plus the write ones for the actions you want, and leave users.export off.
Open Connections → Braze in Memtro and paste the REST API key and the REST endpoint shown next to it, not the SDK endpoint.
An administrator grants actions such as trigger a campaign by name, only to the teams that may message customers.
Ask how the onboarding Canvas has performed this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Braze tools are the same everywhere.
Only when you ask, and only what it has been granted: create a Content Block (as a draft unless told otherwise); update a Content Block; create an email template; update an email template; send an API-triggered campaign to named users; send an API-triggered Canvas to named users; subscribe or unsubscribe named users from a subscription group. 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.
REST API key and REST endpoint. In the Braze dashboard, open Settings → APIs and Identifiers → API Keys → Create API Key. Tick the read permissions, plus the write ones for the actions you want, and leave users.export off.
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