A missing invoice email
Sarah Chen, finance manager at Acme Ltd, asked whether the invoice email to BigCo had arrived. Memtro read the activity and found it hard-bounced, with the SMTP response saying the mailbox did not exist.
Did that email get delivered, and why did it bounce?
SMTP2GO connects Memtro to your transactional email. It reads what happened to sent emails, from delivered to bounced, rejected, opened or clicked, with the SMTP response, the suppression list, templates, sender domains with DKIM and return-path status, this cycle's quota and rates, sending history and subaccounts. When asked, and once an administrator has granted the action by name, it can send an email to real people, billed against the quota, suppress or unsuppress an address, add, change or delete a template and re-check a sender domain. Email bodies in the activity log are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right SMTP2GO tool, reads what it needs, and answers with the source cited.
These tools change something in SMTP2GO. 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 SMTP2GO for you. Each event can start a job, with the event as its input. SMTP2GO sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce SMTP2GO 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.
Did yesterday's invoice email to Northwind get delivered?
Why did emails to bigco.example bounce this week?
How much of this month's quota have we used?
Is our sending domain's DKIM verified?
Remove the bounce suppression on accounts@northwind.example
Sarah Chen, finance manager at Acme Ltd, asked whether the invoice email to BigCo had arrived. Memtro read the activity and found it hard-bounced, with the SMTP response saying the mailbox did not exist.
Dan Fletcher, support lead at Northwind, said a customer's mailbox was working again and asked Memtro to stop blocking it. Memtro lifted the bounce suppression in SMTP2GO, so mail to that address is sent again. Nobody was notified.
The teams that lean on SMTP2GO most, a question each of them asks, and what they connect beside it.
A record in SMTP2GO 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 app.smtp2go.com, open Sending → API Keys → Add API Key and describe it as Memtro.
Under Permissions, tick the reads Memtro should use, and Email send, Suppression, Template or Sender domain verify only for the actions you want. Save and copy the key, which starts api-.
In Memtro, open Connections → SMTP2GO and paste it into API key. Set Region to your account's region if you know it.
Ask your first question: did yesterday's invoice email to Northwind get delivered?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The SMTP2GO tools are the same everywhere.
Only when you ask, and only what it has been granted: send an email (billed against the monthly quota and delivered to real people); suppress an email address or domain (SMTP2GO then refuses to send to it); remove a manual or bounce suppression from an address; add an email template; change an email template; delete an email template (sends that use it start failing); re-check a sender domain's DNS verification. 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 optional region. In app.smtp2go.com, open Sending → API Keys → Add API Key and describe it as 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 SMTP2GO 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