Before a meeting
Ahead of a call with Northwind, the founder asks what folk holds on them. Memtro reads the company with its industry and size, the people there with their titles, and the latest notes, with who wrote each and when.
What you know about a contact in folk, and who sits in a group.
Connect folk with an API key, and Memtro reads people with job title, companies, emails and groups, companies with industry, size and funding, notes with author and date, tasks with due date and assignees, groups, and email campaigns. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can add and change people, companies, deals, notes and tasks, log interactions, and send an email campaign that is in review, which emails people outside the company. Deleting a person, company, note or task is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right folk tool, reads what it needs, and answers with the source cited.
These tools change something in folk. 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 folk for you. Each event can start a job, with the event as its input. folk signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce folk 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 did we last note about Acme?
Who is in the Investors group?
Which of my folk tasks are due this week?
What do we know about Priya Sharma at Brightwave Ltd?
Log that I had coffee with Dan Fletcher today and we discussed the Q1 pilot
Ahead of a call with Northwind, the founder asks what folk holds on them. Memtro reads the company with its industry and size, the people there with their titles, and the latest notes, with who wrote each and when.
After coffee with Priya Nair, the partner asks Memtro to log it. Memtro records the interaction in folk with the date, a title and what was said, and adds a follow-up task due next week assigned to the partner. Nothing is sent to anyone.
The teams that lean on folk most, a question each of them asks, and what they connect beside it.
A record in folk 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 folk open Workspace settings → API and create an API key, which acts as the user who created it, so Memtro sees what that user sees
In Memtro open Connections → folk, paste the API key and connect
A public note Memtro adds is visible to the whole workspace, and a person or company it adds is visible to the workspace
Ask what you last noted about a company
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The folk tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a person or company; create a task on a person or company; log an interaction with a person or company; add a person; change a person's details, companies or groups; add a company; change a company's details or groups; mark a task done; reopen a task; change a task's title, due date, assignees or visibility; edit a note; create a deal or other object in a group; change a deal or other object in a group; delete a note; delete a task; delete a person; delete a company; send or schedule an email campaign that is in review. 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 folk open Workspace settings → API and create an API key, which acts as the user who created it, so Memtro sees what that user sees.
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 folk 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