It never arrived
A customer says the receipt never came. Support asks Memtro, which finds the message by recipient, reads its events and reports a hard bounce at 09:14 with Postmark's description and that the address is now deactivated.
What happened to every transactional email your Postmark server sent.
Connect one Postmark server with its Server API token and Memtro finds a message by recipient, tag or subject and follows its delivery, open, click and bounce events, lists bounces, and reports sends, bounces, complaints, opens and clicks. The hourly sync remembers each finished day's totals. When asked, and once an administrator has granted each action by name, it sends emails, one at a time, from a template or up to 50 in a batch, delivered at once to the recipients outside the company and never recalled. It also reactivates bounced addresses and manages suppressions, templates and message streams.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Postmark tool, reads what it needs, and answers with the source cited.
These tools change something in Postmark. 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, then add the address it shows as a webhook in Postmark, choosing the same kinds; the tab shows Postmark's own steps. Each event can start a job, with the event as its input. Postmark sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Postmark 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 the password reset to priya@northwind.co.uk on 3 November get delivered?
Which addresses hard-bounced this week and are now deactivated?
What were our bounce rate and spam complaint rate in October?
What happened to the receipt tagged order-confirmation sent to jo@acme.com yesterday?
Reactivate jo@acme.com now that their mailbox is fixed and resend the receipt
A customer says the receipt never came. Support asks Memtro, which finds the message by recipient, reads its events and reports a hard bounce at 09:14 with Postmark's description and that the address is now deactivated.
Joe Martin at Acme says his mailbox is fixed. Support asks Memtro to reactivate his address and resend the receipt. Memtro checks the bounce can be reactivated, reactivates it, then sends the receipt template to him from the confirmed sender, delivered at once.
The teams that lean on Postmark most, a question each of them asks, and what they connect beside it.
A record in Postmark 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 Postmark open Servers → the server → API Tokens and copy a Server API token. It reaches only that server's messages, bounces, statistics, templates and streams, and with it Memtro can send from that server once the actions are granted
To see the account's servers, domains and sender signatures too, copy an Account API token from Account → API Tokens. Only the account owner and admins can see it
In Memtro open Connections → Postmark, paste the Server API token (and the account token if you have one) and connect
Ask what happened to the email a customer says never arrived
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Postmark tools are the same everywhere.
Only when you ask, and only what it has been granted: send an email from a confirmed sender to the recipients given; send an email rendered from a template; send up to 50 separate emails in one batch; reactivate an address Postmark deactivated after a bounce; suppress addresses on a message stream, or lift their suppression; create, edit or delete a template; create a message stream, or archive one; retry a failed inbound message. 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. An hourly sync anchors recently changed Postmark records into memory as entities.
Server API token. In Postmark open Servers → the server → API Tokens and copy a Server API token. It reaches only that server's messages, bounces, statistics, templates and streams, and with it Memtro can send from that server once the actions are granted.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Postmark, choosing the same kinds; the tab shows Postmark's own steps. 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