Ask how many people joined your newsletter this month, and how the last issue did.
Connect Buttondown with an API key and Memtro reads subscribers with open and click rates, emails as drafts, scheduled or sent with opens and clicks, reader comments, delivery events, tags and private notes. A key belongs to one newsletter. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can add notes and tags, draft and edit emails, send a test to named people, publish an issue to the whole list, and add, update or delete subscribers. Anything sent cannot be unsent, and deletions are permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Buttondown tool, reads what it needs, and answers with the source cited.
These tools change something in Buttondown. 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, choose the kinds you want, and Memtro registers its address with Buttondown for you. Each event can start a job, with the event as its input. Buttondown signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Buttondown 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 subscribed this month?
How did last week's issue do on opens and clicks?
Why did subscribers unsubscribe in March?
What did readers say in the comments on the latest email?
Send the draft of Friday's issue to Priya and me as a test
The founder asks how the newsletter grew in October. Memtro reads subscribers by signup date and type, and answers that 312 people joined, 41 unsubscribed, mostly giving too many emails as the reason, and 18 became premium subscribers.
Priya Sharma has written Friday's issue and asks Memtro to send her and Tom Hughes a test. Memtro sends the draft to just those two addresses. After she approves it, she asks Memtro to publish it, and Buttondown emails every subscriber in its audience.
The teams that lean on Buttondown most, a question each of them asks, and what they connect beside it.
A record in Buttondown 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 Buttondown open Settings → API and copy the key. If it is not there, look for Programming or API keys. The API reference does not say which plan includes API access
A key belongs to one newsletter, so connect each newsletter separately. Creating tags needs the Basic plan or higher, and only the newsletter owner's key can moderate comments
In Memtro open Connections → Buttondown, paste the API key and connect
Ask how many people subscribed this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Buttondown tools are the same everywhere.
Only when you ask, and only what it has been granted: add a private note to a subscriber, email or other record; create a tag (refused if the name already exists); write a new email as a draft (never sent by this); edit an email's subject, body, description, slug or comment setting (never its status or schedule); send a draft to named subscribers or addresses (they receive it); publish a draft, emailing every subscriber in its audience; send one existing email to one subscriber; add a subscriber (refused if the address exists); update a subscriber's email, notes, tags or type, including unsubscribing them; delete a subscriber (permanent); delete an email (permanent); rename or recolour a tag; delete a tag (permanent); approve a reader comment or mark it as spam. 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 Buttondown open Settings → API and copy the key. If it is not there, look for Programming or API keys. The API reference does not say which plan includes API access.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Buttondown for you. 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