After the send
The day after the Acme newsletter goes out, the marketing lead asks how it did. Memtro reads the campaign's report: 4,820 sent, a 38% unique open rate, a 4.1% click rate, 12 bounces and 9 unsubscribes.
Ask how the last EmailOctopus campaign did, and how many subscribers each list has.
Connect EmailOctopus with an API key and Memtro reads lists with subscribed, unsubscribed and pending counts, a list's contacts and tags, campaigns with subject, sender, status and sent date, and a campaign's results: sends, opens, clicks, bounces and unsubscribes. Email bodies are never read. 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, update or unsubscribe contacts, start an automation for one contact, and manage lists, tags and fields. Subscribing someone can email them, and deleting a contact or list is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right EmailOctopus tool, reads what it needs, and answers with the source cited.
These tools change something in EmailOctopus. 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, then add the address it shows as a webhook in EmailOctopus, choosing the same kinds; the tab shows EmailOctopus's own steps. Each event can start a job, with the event as its input. EmailOctopus signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce EmailOctopus 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 last campaign do on opens and clicks?
How many subscribers are on the newsletter list?
Who unsubscribed from the customers list this month?
Add priya.sharma@globex.com to the newsletter list as pending
Tag everyone from yesterday's webinar sign-ups with webinar-2026
The day after the Acme newsletter goes out, the marketing lead asks how it did. Memtro reads the campaign's report: 4,820 sent, a 38% unique open rate, a 4.1% click rate, 12 bounces and 9 unsubscribes.
A Northwind customer emails asking to stop hearing from the company, and Dan Fletcher asks Memtro to take her off. Memtro unsubscribes her from the customers list, so she receives none of its campaigns or automations, and confirms the status change.
The teams that lean on EmailOctopus most, a question each of them asks, and what they connect beside it.
A record in EmailOctopus 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 EmailOctopus open Account settings → API keys and create a key. Keys made for the old v1 API do not work, so create a new one
The key can do whatever an administrator grants Memtro by name, from reading reports to deleting lists
In Memtro open Connections → EmailOctopus, paste the API key and connect
Ask how the last campaign did
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The EmailOctopus tools are the same everywhere.
Only when you ask, and only what it has been granted: create a new, empty tag on a list, rename a tag, or delete one; add a contact to a list, or create-or-update one by email, with an explicit status (subscribed or pending can email them); update a contact's email, fields, tags or status, or unsubscribe them; delete a contact from a list (permanent); start an API-triggered automation for one contact (it emails them); create, rename or delete a list (deleting removes its contacts, permanently); add a field to 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.
API key. In EmailOctopus open Account settings → API keys and create a key. Keys made for the old v1 API do not work, so create a new one.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in EmailOctopus, choosing the same kinds; the tab shows EmailOctopus's own steps. 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