Did that email reach them, and how is our sending doing?
Resend shows the email your team has sent, with recipients, subject and the last delivery event, such as delivered, bounced or opened. It reports sent, delivered, opened, clicked, bounced and complained figures for a date range, and reads broadcasts, segments, contacts, sending domains and templates. Email bodies are never returned. When asked and granted, it can send an email or a broadcast now or later, which reaches real recipients and cannot be recalled, cancel scheduled sends, edit drafts, add, change or delete contacts and segments, and edit, publish or delete templates. Deleting a contact, draft or template is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Resend tool, reads what it needs, and answers with the source cited.
These tools change something in Resend. 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 Resend for you. Each event can start a job, with the event as its input. Resend signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Resend 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.
Was the invoice email to Globex delivered?
What was our bounce rate last week?
Which broadcasts are still drafts?
Has dan@northwind.com unsubscribed?
Schedule the November newsletter broadcast for 9am Tuesday
Priya Sharma, finance manager at Acme Ltd, asked whether the invoice email to Northwind was delivered. Memtro found the email and showed its last event as delivered, with the time. She closed the query without chasing anyone.
Maya Okafor, marketing lead at BigCo, reviewed the November broadcast draft and asked Memtro to send it on Tuesday morning. Memtro scheduled it in Resend, and at 9am every contact in the Customers segment who had not unsubscribed was emailed.
The teams that lean on Resend most, a question each of them asks, and what they connect beside it.
A record in Resend 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.
AgentMail
Fireflies.ai
SendGrid
Avoma
Missive
tl;dv
Grain
Fathom Video
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
Textmagic
SMTP2GO
MailerSend
InfobipIn the Resend dashboard, open API Keys, choose Create API Key and name it Memtro.
Set Permission to Full access, since a Sending access key cannot read anything. A Full access key carries the whole team's access, sending included. Copy the key, as Resend shows it once.
In Memtro, open Connections → Resend and paste it into API key.
Ask "Was the invoice email to Globex delivered?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Resend tools are the same everywhere.
Only when you ask, and only what it has been granted: create a broadcast as a draft (never sent or scheduled); create an email template (left as a draft, not published); send an email now or at a set time (the recipients are emailed); cancel a scheduled email before it sends; send or schedule a broadcast (everyone in its segment is emailed); cancel a queued or scheduled broadcast; edit a draft broadcast; delete a draft broadcast (permanent); add a contact, optionally to segments; edit a contact's name, email or unsubscribe status; delete a contact (permanent); add a contact to a segment; remove a contact from a segment; create a segment; edit an email template; publish an email template so it can be used to send; delete an email template (permanent). 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 the Resend dashboard, open API Keys, choose Create API Key and name it Memtro.
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 Resend 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
