Next steps recalled
Sarah Chen, account director at BigCo, asked what the next steps were from yesterday's call with Northwind. Memtro read the meeting's next-step highlights and summary. She had the list in her follow-up email within minutes.
What were the next steps from yesterday's client call?
MeetGeek connects Memtro to your AI meeting notes. It reads recorded meetings with title, time, host and participants, each meeting's AI summary, and the transcript by speaker. It also reads highlights such as action items and next steps, and insight scores and themes. When asked and granted, it can send the recorder into a live meeting, submit a recording at a URL for analysis, or delete a meeting. MeetGeek can also tell Memtro when an uploaded recording finishes or fails analysis, and a job can start on it. The key sees only your meetings and those shared with you.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right MeetGeek tool, reads what it needs, and answers with the source cited.
These tools change something in MeetGeek. 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 MeetGeek, choosing the same kinds; the tab shows MeetGeek's own steps. Each event can start a job, with the event as its input. MeetGeek signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce MeetGeek 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.
What were the next steps from yesterday's client call?
Summarise the product review meeting on Tuesday.
What did Dan Fletcher say about pricing in the Northwind call?
Which themes came up most in this week's sales calls?
Send the recorder into the 3pm Zoom call.
Sarah Chen, account director at BigCo, asked what the next steps were from yesterday's call with Northwind. Memtro read the meeting's next-step highlights and summary. She had the list in her follow-up email within minutes.
Maya Okafor, product manager at Acme Ltd, asked Memtro to record a customer interview she could not attend. With the action granted, Memtro sent the MeetGeek recorder in by the join link. Everyone in the meeting saw it join and record.
The teams that lean on MeetGeek most, a question each of them asks, and what they connect beside it.
A record in MeetGeek 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 MeetGeek, open Integrations → Public API and generate the API key. It is yours and sees your meetings and those your teams share.
In Memtro, open Connections → MeetGeek and paste the API key. Set the Region to EU or US if the key is refused.
An administrator grants the actions by name, such as Delete a meeting and its notes permanently, to the teams that may use them. Events are turned on from the connection's Events tab, and the address is then pasted into MeetGeek's Public API card.
Ask "What were the next steps from yesterday's client call?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The MeetGeek tools are the same everywhere.
Only when you ask, and only what it has been granted: send the MeetGeek recorder bot to join a live meeting; submit a recording at a URL for transcription and analysis; delete a meeting and its notes permanently. 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. In MeetGeek, open Integrations → Public API and generate the API key. It is yours and sees your meetings and those your teams share.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in MeetGeek, choosing the same kinds; the tab shows MeetGeek'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