Catching up on decisions
Sarah Chen, head of product at Acme Ltd, missed Monday's roadmap sync. Memtro read the meeting's note and recording recap, and told her the decisions taken and the action items assigned to her.
What was decided in Monday's sync, and which action items are still open?
Fellow connects Memtro to your meeting notes, as the key's owner sees them. It reads notes with their text, action items by status, due date and assignee, and recordings with Fellow's AI recap. Transcripts are never read. When asked, and once an administrator has granted the action by name, it adds text to the top or end of an agenda, edits or replaces an agenda, renames notes, and completes, reopens or archives action items. Everyone with access to the note sees each change. Replacing a whole agenda, archiving an action item and deleting a note cannot be undone.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Fellow tool, reads what it needs, and answers with the source cited.
These tools change something in Fellow. 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, choose the kinds you want, and Memtro registers its address with Fellow for you. Each event can start a job, with the event as its input. Fellow signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Fellow 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 was decided in Monday's sync?
Which of my action items are still open?
What did we agree with Northwind in last week's call?
Add "Review the Q4 hiring plan" to the agenda for Thursday's leadership meeting.
Mark my action item to send the Globex proposal as done.
Sarah Chen, head of product at Acme Ltd, missed Monday's roadmap sync. Memtro read the meeting's note and recording recap, and told her the decisions taken and the action items assigned to her.
Dan Fletcher, an engineering manager at Acme Ltd, asked Memtro to put the release checklist at the top of Thursday's agenda and mark his two finished action items done. Memtro added his approved wording to the top of the note and completed both items. Attendees saw the changes in Fellow.
The teams that lean on Fellow most, a question each of them asks, and what they connect beside it.
A record in Fellow 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 Fellow, go to User settings → Developer API and create a new API key named Memtro. Copy it, as it is shown once.
If there is no Developer API section, a workspace admin must enable the API under Workspace settings → Security.
In Memtro, open Connections → Fellow. Enter the Workspace subdomain, the word before .fellow.app, and paste the API key.
Ask "What was decided in Monday's sync?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Fellow tools are the same everywhere.
Only when you ask, and only what it has been granted: append text to the end of a meeting note's agenda, which everyone with access to the note sees; add text to the top of a meeting note's agenda; replace one exact piece of text in a note's agenda, or delete it; replace a note's whole agenda; rename a meeting note; delete a meeting note (Super Admin key); mark an action item done, or reopen it; archive an action item as won't do. 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.
Workspace subdomain and API key. In Fellow, go to User settings → Developer API and create a new API key named Memtro. Copy it, as it is shown once.
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 Fellow 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