Monthly email review
The founder asks how October's emails did. Memtro reads Drip's email metrics for the month: 18,400 sends, 7,500 opens, 212 orders and the revenue they brought, and names the three single-email campaigns with the most sends.
Ask how last month's Drip emails performed, and draft a campaign for someone to schedule.
Connect Drip with your personal API token and Memtro reads the Drip accounts you can see: subscribers, tags, single-email campaigns, email series and workflows, and email performance for a period, with sends, opens, clicks, orders and revenue. 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 draft, test, schedule or send a campaign, update subscribers and tags, unsubscribe people, and start or pause workflows and series. Sending emails real customers and cannot be recalled, and a tag can start a workflow.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Drip tool, reads what it needs, and answers with the source cited.
These tools change something in Drip. 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 Drip for you. Each event can start a job, with the event as its input. Drip signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Drip 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 last month's emails perform on opens, clicks and revenue?
Which active subscribers are tagged trial-started?
Which email series are active, and how many subscribers are in each?
Create a draft campaign called November product update and send me a test
Unsubscribe dan.fletcher@acme.com from all mailings
The founder asks how October's emails did. Memtro reads Drip's email metrics for the month: 18,400 sends, 7,500 opens, 212 orders and the revenue they brought, and names the three single-email campaigns with the most sends.
Priya Nair asks Memtro to prepare the November product update for the Globex customers segment. Memtro creates the draft, sets its audience to that saved segment and sends her a test. Once she approves it, Memtro schedules it for 9am Thursday, when Drip emails everyone in the segment.
The teams that lean on Drip most, a question each of them asks, and what they connect beside it.
A record in Drip 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 Drip open User Settings → API Token and copy your personal token: Memtro sees the Drip accounts you can see and can change what you can
If you have more than one Drip account, note the Account ID, the number in your Drip address (getdrip.com/9999999/...)
In Memtro open Connections → Drip, paste the API token, and the Account ID if needed, and connect
Ask how last month's emails performed
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Drip tools are the same everywhere.
Only when you ask, and only what it has been granted: create or edit a draft single-email campaign (sends nothing by itself); set a draft campaign's audience to everyone or to saved segments; send a test copy of a campaign to up to five team addresses; schedule a single-email campaign or send it now to its audience, or unschedule it back to draft; delete a single-email campaign that is not sending; create or update a subscriber, apply or remove a tag (either can start a workflow that emails them); unsubscribe someone from all mailings, or remove them from one email series; start someone on a workflow or take them off it; activate or pause a workflow or an email series (activating starts emailing people). 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 Drip open User Settings → API Token and copy your personal token: Memtro sees the Drip accounts you can see and can change what you can.
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 Drip 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