Ask what was agreed on a customer call, with Fathom's summary and action items.
Connect Fathom Video with an API key and Memtro reads the meetings recorded with Fathom: title, meeting type, when, length, who recorded it, invitees by name and company domain, and whether anyone external was invited. It reads Fathom's summary and action items, and a slice of the transcript by speaker. Participants' email addresses are never passed on. The key is personal, so Memtro sees only its owner's meetings and what is shared with them. It reads on demand and there is no hourly sync. Nothing is written to Fathom Video.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fathom Video tool, reads what it needs, and answers with the source cited.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Fathom Video for you. Each event can start a job, with the event as its input. Fathom Video signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Fathom Video 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.
Fathom Video + MemtroWhat was agreed on Tuesday's call with Northwind?
What action items came out of this week's calls with Acme?
Which calls last week had someone external from Brightwave Ltd invited?
What exactly did Dan Fletcher say about pricing on the BigCo call?
Which meetings did Priya Sharma record this month?
Before writing a follow-up email, the account lead asks what was agreed on Tuesday's call with Northwind. Memtro finds the meeting, reads Fathom's summary and action items, and answers with the three agreed next steps and who owns each one.
Support hears that Acme was promised a March delivery date. Priya Sharma asks Memtro what Dan Fletcher said about it on the Acme call. Memtro reads that part of the transcript and quotes his words with the time into the recording.
The teams that lean on Fathom Video most, a question each of them asks, and what they connect beside it.
A record in Fathom Video 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
ClickSend
OneSignal
Bird
MeetGeek
Sinch
Telnyx
Textmagic
SMTP2GO
MailerSend
InfobipIn Fathom open User Settings → API Access, generate an API key and copy it
The key sees only its owner's recordings and those shared with them, never anyone's private calls; for the whole company's shared calls, use the key of an admin allowed to view all shared calls
Paste it into Connections → Fathom Video in Memtro and connect
Ask what was agreed on the last call with Northwind
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fathom Video tools are the same everywhere.
Not yet. Today every Fathom Video 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.
API key. In Fathom open User Settings → API Access, generate an API key and copy it.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Fathom Video for you. 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
