Is this person still subscribed to our Flodesk emails, and which segments are they in?
Flodesk reads your email subscribers and segments. Look up one subscriber by email for their status, such as active, unsubscribed or bounced, how they joined, their segments and when they were added. Segments come with active subscriber counts and type. When asked, and once an administrator has granted the action by name, it adds or updates subscribers, moves them in or out of segments, enrols them in workflows or removes them, unsubscribes them from all email, and creates segments and custom fields. Adding someone to a segment or workflow can start emails to them.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Flodesk tool, reads what it needs, and answers with the source cited.
These tools change something in Flodesk. 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 Flodesk 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.
Flodesk + MemtroIs jo@example.com still subscribed?
How did sam@example.com join our list?
Which segments is maya@example.com in?
How many active subscribers are in the VIP segment?
Add maya@example.com to the Workshop waitlist segment
Sarah Chen, customer success lead at Northwind, hears from a client that the newsletter stopped arriving. Memtro looks up the client's email and finds the status bounced. It also gives the segments they were in and when they were added.
Dan Fletcher, marketing coordinator at BigCo, forwards a reader's request to stop all emails. He asks Memtro to unsubscribe her. Memtro unsubscribes the address in Flodesk, and she stops receiving every campaign and workflow email.
The teams that lean on Flodesk most, a question each of them asks, and what they connect beside it.
A record in Flodesk 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
LoyaltyLion
Benchmark Email
Braze
Sender
Rewardful
Mailshake
SurveySparrow
RetentlyIn Flodesk, open My Account → Integrations → API keys. You need a paid Flodesk plan.
Choose Create API key, name it Memtro, and copy the key, which is shown once. The key has full access to the account, so Memtro writes only what an administrator grants.
In Memtro, open Connections → Flodesk and paste it into API key.
Ask "Is jo@example.com still subscribed?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Flodesk tools are the same everywhere.
Only when you ask, and only what it has been granted: add or update a subscriber, optionally into segments (may email them); add a subscriber to segments (may start segment workflows); remove a subscriber from segments; unsubscribe a subscriber from all email; add a subscriber to a workflow (they receive its emails); remove a subscriber from a workflow; create a segment; 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 key. In Flodesk, open My Account → Integrations → API keys. You need a paid Flodesk plan.
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