EmailOctopus + Memtro

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.

In Memtro

What you can do with EmailOctopus in Memtro

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.

What it does

  1. 01Lists with double opt-in setting, subscribed, unsubscribed and pending counts, and their tags
  2. 02A list's contacts by status, tag, created or updated date, with email, name and tags
  3. 03Campaigns with subject, preview text, status, sender, lists and created and sent dates, and each one's opens, clicks, bounces and unsubscribes
  4. 04When asked and granted, adds or updates a contact with an explicit status, which can start automations or send a confirmation email, unsubscribes one, or deletes one permanently
  5. 05When asked and granted, starts an API-triggered automation for one contact, which then emails them
  6. 06When asked and granted, creates, renames or deletes tags, lists and fields, where deleting a list removes all its contacts permanently

Acts when asked

When you ask it to

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.

  1. 01Create a new, empty tag on a list, rename a tag, or delete one
  2. 02Add a contact to a list, or create-or-update one by email, with an explicit status (subscribed or pending can email them)
  3. 03Update a contact's email, fields, tags or status, or unsubscribe them
  4. 04Delete a contact from a list (permanent)
  5. 05Start an API-triggered automation for one contact (it emails them)
  6. 06Create, rename or delete a list (deleting removes its contacts, permanently)
  7. 07Add a field to a list

Events

When it happens

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 webhooks
  • 01A contact was added to a list
  • 02A contact was changed
  • 03A contact was deleted
  • 04A contact unsubscribed
  • 05An email to a contact bounced
  • 06A contact marked an email as spam
  • 07A contact opened an email
  • 08A contact clicked a link
In practice

Ask it like you would a colleague

Once 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.

EmailOctopus + Memtro
  • 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

01

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.

02

Honouring an opt-out

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.

Teams

Where it fits

The teams that lean on EmailOctopus most, a question each of them asks, and what they connect beside it.

Better together

Works with

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.

Also in Marketing automation

Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.

Setup

How to connect

Connect withAPI key
  1. 1

    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

  2. 2

    The key can do whatever an administrator grants Memtro by name, from reading reports to deleting lists

  3. 3

    In Memtro open Connections → EmailOctopus, paste the API key and connect

  4. 4

    Ask how the last campaign did

Also works from

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.

FAQ

Questions

Can Memtro change anything in EmailOctopus?+

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.

Who can use a EmailOctopus connection?+

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.

Does Memtro store my EmailOctopus data?+

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.

How do I connect EmailOctopus?+

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.

Can EmailOctopus start a job?+

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.

Connect EmailOctopus in a few minutes

Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.

Where agents remember your company

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