Did that notification reach the person, and if not, why not?
Courier reads your notification delivery log, newest first, with each message's status, reason or error, template, recipient id and the channels and providers it went through. It also lists templates with their routing and brands with their colours. Recipient addresses are never shown. When asked, and once an administrator has granted the action by name, it sends and resends messages, starts journeys, sends or schedules broadcasts, publishes or archives templates, updates profiles, subscribes users to lists and manages brands. Messages and broadcasts reach people outside the company and cannot be recalled once delivered.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Courier tool, reads what it needs, and answers with the source cited.
These tools change something in Courier. 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 Courier, choosing the same kinds; the tab shows Courier's own steps. Each event can start a job, with the event as its input. Courier signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Courier 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.
Why didn't the welcome email arrive for user 42?
Which messages were undeliverable today, and why?
Which providers did the last password reset go through?
Which templates send on every channel?
Resend the welcome email to user 42.
Dan Fletcher, support lead at BigCo, asks why user 42 never got a welcome email. Memtro filters the delivery log by that recipient id and finds the message marked undeliverable with the provider's error. It opens the message to show the channel and provider it tried.
Sarah Chen, product engineer at Acme Ltd, finds that user 42's email address was wrong. She asks Memtro to correct the profile and send the welcome email again. Memtro merges the new address into the user's Courier profile and resends the message, which Courier delivers to the new address.
The teams that lean on Courier most, a question each of them asks, and what they connect beside it.
A record in Courier 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 Courier, open Settings → API Keys and choose the Production environment.
Copy a published key, which starts pk_, not a draft key starting dk_.
In Memtro, open Connections → Courier and paste the API key. Set Datacenter to "eu" if you sign in at app.eu.courier.com.
Ask "Why didn't the welcome email arrive for user 42?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Courier tools are the same everywhere.
Only when you ask, and only what it has been granted: send a message to a user, email address, phone number, list or audience (notifies them); cancel a message still being delivered; resend a message to its original recipient (notifies them again); start a journey run for one user (it may message them); cancel journey runs by run id or cancelation token; create a draft broadcast; send a broadcast now to a list or audience (notifies every member); schedule a broadcast for a list or audience; archive a broadcast; publish a template's draft or an earlier version (changes live sends); archive a template (new sends using it fail); merge values into a user's profile; subscribe a user to lists (creates missing lists); create a brand; delete a brand (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 and optional datacenter. In Courier, open Settings → API Keys and choose the Production environment.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Courier, choosing the same kinds; the tab shows Courier'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
