Who clicked
The marketing lead asks who clicked in Tuesday's campaign. Memtro returns the campaign's stats, then the subscribers who clicked with their opens and clicks, so sales can follow up the ones who are already customers.
Campaign results, group health and who opened what, straight from MailerLite.
Connect MailerLite with an API token and Memtro reads subscribers with their fields and engagement, groups with counts and rates, campaigns with opens, clicks, unsubscribes and bounces and who opened or clicked, sign-up forms and automations. It reads on demand and there is no hourly sync. When asked, and once an administrator has granted each action by name, it can add, update and delete subscribers, manage groups and custom fields, and draft, schedule or send campaigns. Sending emails the whole audience outside the company and cannot be undone, and forgetting a subscriber erases them permanently after 30 days.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right MailerLite tool, reads what it needs, and answers with the source cited.
These tools change something in MailerLite. 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 MailerLite for you. Each event can start a job, with the event as its input. MailerLite signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce MailerLite 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 'Autumn offers' campaign do, and who clicked?
Which groups have the highest open rate, and which has the most bounces?
Is tom.ashby@example.co.uk subscribed, which groups is he in, and does he open anything?
Is the welcome automation still running and how many people are queued in it?
Add jane.cole@northwind.example to the Webinar group
The marketing lead asks who clicked in Tuesday's campaign. Memtro returns the campaign's stats, then the subscribers who clicked with their opens and clicks, so sales can follow up the ones who are already customers.
Priya Shah asks Memtro to send the approved November newsletter draft to the Customers group at 9am on Thursday. Memtro reads the campaign, checks its subject and groups, and schedules it in MailerLite. It stays cancellable back to draft until it starts, and then emails every subscriber in the group.
The teams that lean on MailerLite most, a question each of them asks, and what they connect beside it.
A record in MailerLite 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 MailerLite open Integrations → MailerLite API → Generate new token, name it and copy the token: it is shown once
This is for the current MailerLite at dashboard.mailerlite.com. A token from MailerLite Classic uses a different API and will not work
In Memtro open Connections → MailerLite, paste the API token and connect. MailerLite allows 120 requests a minute per token
Ask how the last campaign did or who clicked it
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The MailerLite tools are the same everywhere.
Only when you ask, and only what it has been granted: add a subscriber, or update the one with that email, optionally into groups; update a subscriber's fields, status or full set of groups; delete a subscriber (their data is kept in case they resubscribe); forget a subscriber under GDPR, erased permanently after 30 days; create a group; rename a group; delete a group permanently; add a subscriber to a group; remove a subscriber from a group; draft a regular email campaign; edit a draft campaign; send a campaign now or schedule it, emailing its whole audience; cancel a scheduled campaign back to draft; delete a campaign permanently; create a custom subscriber field. 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 token. In MailerLite open Integrations → MailerLite API → Generate new token, name it and copy the token: it is shown once.
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 MailerLite 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