After a phishing test
Maya Okafor, IT manager at Northwind, asked how the October phishing test went. Memtro read the test's aggregate counts and gave the phish-prone percentage and how many people reported it, without naming anyone who clicked.
How did the last phishing test go, and who is behind on training?
KnowBe4 connects Memtro to your security awareness reporting, and it reads and nothing else. It reads users with department and groups, and groups with member counts and their aggregate risk score. It reads phishing campaigns and each test's aggregate results, such as opened, clicked and reported counts and the phish-prone percentage. It reads training campaigns and who has passed, started or fallen past due on each module. Phishing results are read per campaign only and never name who clicked. Per-person risk scores are not returned either.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right KnowBe4 tool, reads what it needs, and answers with the source cited.
Once KnowBe4 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.
How did the October phishing test go?
Who is past due on security training?
Which groups have the highest risk score?
What was the phish-prone percentage on the finance team's last campaign?
Has Dan Fletcher completed this year's security training?
Maya Okafor, IT manager at Northwind, asked how the October phishing test went. Memtro read the test's aggregate counts and gave the phish-prone percentage and how many people reported it, without naming anyone who clicked.
Priya Sharma, compliance lead at Acme Ltd, asked who was past due on security training. Memtro read the enrolments for the annual campaign and listed the people marked Past Due with their module.
The teams that lean on KnowBe4 most, a question each of them asks, and what they connect beside it.
A record in KnowBe4 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.
Open the Reporting API Management Console at training.knowbe4.com/app/api_tokens/reporting, or the same page on your own server.
Generate a key and copy it. A User Event API key will not work.
In Memtro, open Connections → KnowBe4 and paste it into Reporting API key. Set Server to "eu", "ca", "uk" or "de" if you sign in there.
Ask: how did the October phishing test go?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The KnowBe4 tools are the same everywhere.
Not yet. Today every KnowBe4 tool reads, searches or lists. When the connector gains actions, each is marked, granted by name per team and used only when a person asks for exactly that, so nothing is created, sent, updated or deleted until you say so.
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.
Reporting API key and server. Open the Reporting API Management Console at training.knowbe4.com/app/api_tokens/reporting, or the same page on your own server.
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