Newsletter results check
Maya Okafor, marketing manager at Acme Ltd, asked how the October newsletter did. Memtro read the sent campaign and gave its recipients, opens, clicks, bounces and open and click rates.
How did last week's newsletter do, and who has unsubscribed since?
Sender gives you email marketing as plain answers. You see subscribers with their status and groups, groups and segments with their counts, campaigns by status with opens, clicks and bounces, and automation workflows with their send and open figures. When asked and granted, Memtro can add, update, unsubscribe or delete subscribers, manage group membership, create groups, draft, copy, send, schedule or cancel campaigns, start a workflow for someone, record a custom event and send a transactional email. Worth knowing: a Sender token has no scopes and carries full access to the account, and the tools never return a campaign's HTML.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Sender tool, reads what it needs, and answers with the source cited.
These tools change something in Sender. 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 Sender 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 did last week's newsletter perform?
Which campaigns are scheduled to go out?
How many subscribers in the Customers group have bounced?
Which automation workflows are active, and what are their open rates?
Unsubscribe jo@example.com from our emails.
Maya Okafor, marketing manager at Acme Ltd, asked how the October newsletter did. Memtro read the sent campaign and gave its recipients, opens, clicks, bounces and open and click rates.
Dan Fletcher, head of growth at Northwind, asked Memtro to schedule the draft product update for Tuesday at 9am. Memtro read the campaign first, then scheduled it to email its whole audience, and the team saw it as scheduled in Sender. It can still be cancelled before then.
The teams that lean on Sender most, a question each of them asks, and what they connect beside it.
A record in Sender 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 Sender, go to Account settings, then API access tokens, and create a token. It has no scopes and carries full access to the account.
In Memtro, open Connections → Sender and paste the token into API access token.
An administrator grants the actions by name, such as Send campaign or Delete subscribers, to the teams that may use them.
Ask how last week's newsletter performed.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Sender tools are the same everywhere.
Only when you ask, and only what it has been granted: add a subscriber; update a subscriber's name, groups or status (including unsubscribing them); add subscribers to a group; remove subscribers from a group; delete subscribers; create a group; create a draft campaign; copy a campaign; send a campaign now; schedule a campaign; cancel a scheduled campaign; delete a campaign; start a workflow for an email address; record a custom event for a subscriber; send a transactional email. 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 access token. In Sender, go to Account settings, then API access tokens, and create a token. It has no scopes and carries full access to the account.
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