Which password reset emails bounced today, and which workflow runs hit errors?
Knock connects Memtro to your notification infrastructure. It reads messages by workflow, channel, tenant and status, with their delivery and engagement events, and workflow runs per recipient with their errors. It also reads users by id, tenants, schedules and audience members. When asked and granted, it can trigger, cancel or schedule a workflow, delete schedules, manage users, tenants, audiences and object subscriptions, and mark messages read or archived. Knock can also tell Memtro as messages are delivered, bounce or fail, and a job can start on it. Message contents and users' names, emails and phones are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Knock tool, reads what it needs, and answers with the source cited.
These tools change something in Knock. 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 Knock, choosing the same kinds; the tab shows Knock's own steps. Each event can start a job, with the event as its input. Knock signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Knock 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.
Which password reset emails bounced today?
Which workflow runs had errors this week?
Show the delivery history of this message.
What schedules are set up for the weekly digest workflow?
Who is in the beta testers audience?
Maya Okafor, product manager at Acme Ltd, asked which password reset emails bounced today. Memtro listed the bounced messages for that workflow with their recipient ids and times. She passed the list to support to check the addresses.
When a workflow run hit an error at Northwind, Knock told Memtro and a job started. It read the recent runs for that workflow and their error counts, then summarised the pattern for Dan Fletcher, the platform engineer. No notification was resent.
The teams that lean on Knock most, a question each of them asks, and what they connect beside it.
A record in Knock 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 Knock dashboard, open Developers → API keys, pick the environment and copy a secret key starting sk_. The publishable pk_ key will not work.
In Memtro, open Connections → Knock and paste the Secret API key.
An administrator grants the actions by name, such as Trigger a workflow for named users, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then added under Platform → Webhooks in that Knock environment.
Ask "Which password reset emails bounced today?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Knock tools are the same everywhere.
Only when you ask, and only what it has been granted: trigger a workflow for named users (sends real notifications); cancel a triggered workflow by its cancellation key; schedule a workflow for named users (sends at the scheduled times); delete schedules; create or update a user; merge one user into another; delete a user; create or update a tenant; delete a tenant; add users to an audience; remove users from an audience; subscribe users to an object; unsubscribe users from an object; mark a message read, unread, seen, unseen, archived or unarchived. 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.
Secret API key. In the Knock dashboard, open Developers → API keys, pick the environment and copy a secret key starting sk_. The publishable pk_ key will not work.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Knock, choosing the same kinds; the tab shows Knock'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
