How did that campaign perform, and who is on this list?
Iterable shows your campaigns by state, with type, medium, send size, lists and dates, and reports sends, deliveries, opens, clicks, bounces, unsubscribes, conversions and revenue for up to 10 campaigns at a time. It reads lists and their sizes, journeys, templates and one person's profile by email. When asked and granted, it can send an email, text or push to one person, send, schedule, trigger, abort or cancel campaigns, trigger journeys, track events, update profiles and add or remove people on lists. Sends reach real customers and cannot be recalled. A key belongs to one project and one data centre.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Iterable tool, reads what it needs, and answers with the source cited.
These tools change something in Iterable. 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.
Once Iterable 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.
Iterable + MemtroHow did last week's Black Friday campaign perform?
Which campaigns are scheduled?
How many people are on the VIP list?
Which lists is maya@bigco.com on?
Schedule the December offers campaign for Friday at 8am
Maya Okafor, CRM manager at BigCo, asked how the Black Friday campaign performed. Memtro returned its sends, opens, clicks, conversions and revenue as Iterable reports them. She compared it with the previous campaign in the same answer.
Tom Reilly, marketing executive at Acme Ltd, asked Memtro to send him a proof of the webinar invitation and then schedule the campaign for Thursday. Memtro emailed the proof to Tom alone, and once he approved it scheduled the campaign, which messaged everyone on its lists on Thursday.
The teams that lean on Iterable most, a question each of them asks, and what they connect beside it.
A record in Iterable 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
Dotdigital
Flodesk
LoyaltyLion
Benchmark Email
Braze
Sender
Rewardful
Mailshake
SurveySparrow
RetentlyIn Iterable, open Integrations → API Keys and choose New API key.
Choose a server-side key and copy it. A key belongs to one project, so add one connection per project.
In Memtro, open Connections → Iterable, paste it into API key, and set Data centre to "eu" if you sign in at app.eu.iterable.com.
Ask "How did last week's Black Friday campaign perform?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Iterable tools are the same everywhere.
Only when you ask, and only what it has been granted: create a new, empty static list; send an email to one person from an existing campaign (they are emailed); send an SMS to one person from an existing SMS campaign (they are texted); send a push notification to one person from an existing push campaign; send a proof of an email template to one person; create a blast or triggered campaign from a template (not scheduled); send an existing campaign now (its lists are messaged); schedule an existing campaign to send within 7 days; trigger a triggered campaign to given lists (everyone on them is messaged); abort a running campaign; cancel a scheduled or recurring campaign; trigger a journey for one person or a whole list; track a custom event for a person (journeys on it may message them); update a person's profile fields (merged; creates the person if new); add people to a static list; remove people from a list (optionally unsubscribing them from its channel). 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 and data centre. In Iterable, open Integrations → API Keys and choose New API key.
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