How each Campaign Monitor campaign did, who opened or clicked, and who is still subscribed.
Connect Campaign Monitor with the account-level API key and Memtro reads every client's campaigns, each campaign's opens, clicks, bounces, unsubscribes and spam complaints with who did what, the subscriber lists, and one subscriber's state by email. The hourly sync writes each sent campaign into memory. When you ask, and once an administrator has granted the action by name, it can create a draft campaign, send or schedule it, unschedule or permanently delete a campaign, and unsubscribe or delete a subscriber. Sending emails every subscriber on the lists, cannot be recalled once it goes, and may spend credits.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Campaign Monitor tool, reads what it needs, and answers with the source cited.
These tools change something in Campaign Monitor. 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 Campaign Monitor for you. Each event can start a job, with the event as its input. Campaign Monitor signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Campaign Monitor 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 the October newsletter do compared with September's?
Who clicked the pricing link in last week's campaign?
Is priya@acme.com still subscribed to the customers list?
Which campaigns are scheduled to go out this month?
Unsubscribe dan@northwind.com from the product updates list
On Monday the marketing lead asks how Thursday's newsletter landed. Memtro reads the campaign summary and gives recipients, unique opens, clicks, bounces and unsubscribes, then lists who clicked the webinar link, so sales can follow up with the most engaged accounts.
Priya Sharma notices a wrong date in the newsletter scheduled for Thursday and asks Memtro to hold it. Memtro unschedules the campaign, which returns to drafts in Campaign Monitor, and nobody is emailed until it is sent again.
The teams that lean on Campaign Monitor most, a question each of them asks, and what they connect beside it.
A record in Campaign Monitor 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 Campaign Monitor open your profile image → Account settings → API keys and show the account API key, since the account-level key sees every client
Copy the key, and optionally the Default client ID shown under each client on the same page, which is found automatically with one client
In Memtro open Connections → Campaign Monitor, paste the API key and connect
Ask how last month's newsletter did, and who clicked through
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Campaign Monitor tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft campaign from an HTML page's URL, aimed at lists or segments (sends nothing); send a draft campaign to its lists now or schedule it (emails every subscriber on them, may spend credits); unschedule a scheduled campaign back to drafts; delete a campaign (permanent); unsubscribe an email address from a list; delete a subscriber from a list. 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. An hourly sync anchors recently changed Campaign Monitor records into memory as entities.
API key. In Campaign Monitor open your profile image → Account settings → API keys and show the account API key, since the account-level key sees every client.
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 Campaign Monitor 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