Where does this deal sit in our pipeline, and when did we last talk to them?
Affinity connects Memtro to your relationship CRM. It reads companies and their field data, lists and their rows such as your deal-flow pipeline with stage, list fields, notes on companies, people and opportunities with their authors, reminders, and people found by name or email. When asked, and once an administrator has granted the action by name, it can write, edit or delete a note, manage reminders, add a company or person to a list, set a field such as a deal's stage, create or delete a person, and rename or delete an opportunity. Amounts and relationship scores are never shown.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Affinity tool, reads what it needs, and answers with the source cited.
These tools change something in Affinity. 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.
Once Affinity 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.
Affinity + MemtroWhich deals in our pipeline are at term sheet?
When did we last write a note about Northwind?
Which of my reminders are overdue?
Who owns the BigCo opportunity?
Move Northwind to Due diligence on the deal-flow list
Priya Sharma, principal at Acme Ventures, asked what the team knew about Northwind before Monday's partner meeting. Memtro showed Northwind's stage on the deal-flow list and summarised the three latest notes with their authors.
Tom Reilly, partner at BigCo Capital, asked Memtro to move Northwind to due diligence and remind Maya Okafor to request the data room next Friday. Memtro set the stage on the list row and created the reminder, which Affinity may notify Maya about.
The teams that lean on Affinity most, a question each of them asks, and what they connect beside it.
A record in Affinity 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.
Capsule CRM
Copper
Freshsales
Dialpad
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Kommo
Pipeline CRM
KeapIn Affinity, open Settings → Manage Apps → New App, name it Memtro and choose API Key. API keys are on the Scale, Advanced and Enterprise plans, and creating one needs the Generate an API key permission.
Copy the key, which is shown once. It acts as you, and reading companies and list rows needs the Export All Organizations and Export data from Lists permissions.
In Memtro, open Connections → Affinity and paste it into API key.
Ask your first question: which deals in our pipeline are at term sheet?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Affinity tools are the same everywhere.
Only when you ask, and only what it has been granted: write a note on companies, people or opportunities; edit a note's text or what it is attached to; delete a note (permanent, with its replies); create a reminder for a colleague on a company, person or opportunity; change, complete or reopen a reminder; delete a reminder; add a company or person to a list; set a field on a list row, such as moving a deal to another stage; set a field on a company; create a person; delete a person (permanent); rename an opportunity; delete an opportunity (permanent). 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. An hourly sync anchors recently changed Affinity records into memory as entities.
API key. In Affinity, open Settings → Manage Apps → New App, name it Memtro and choose API Key. API keys are on the Scale, Advanced and Enterprise plans, and creating one needs the Generate an API key permission.
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