The month's forecast
Sarah Chen, sales director at Acme Ltd, asked which deals were expected to close this month. Memtro listed them with value, stage, probability and owner, and gave the total.
Which deals close this month, and what happened on them last?
Pipeline CRM connects Memtro to your deals. It reads deals with stage, value, owner, company and people, people and leads with position, company and status, companies, the activities logged on a deal, person or company, tasks and events, and the account's stages, pipelines and categories. When asked, and once an administrator has granted the action by name, it can create and edit deals, people and companies, delete a deal or an activity, log an activity, comment on one, which emails its notify list, and add or complete a task or event. Phone numbers and home details are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Pipeline CRM tool, reads what it needs, and answers with the source cited.
These tools change something in Pipeline CRM. 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 Pipeline CRM, choosing the same kinds; the tab shows Pipeline CRM's own steps. Each event can start a job, with the event as its input. Pipeline CRM signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Pipeline CRM 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.
Which deals are expected to close this month?
What was the last activity on the Northwind deal?
Which leads have I not touched in two weeks?
What tasks are due for me tomorrow?
Log a note on the BigCo deal that pricing was agreed
Sarah Chen, sales director at Acme Ltd, asked which deals were expected to close this month. Memtro listed them with value, stage, probability and owner, and gave the total.
Tom Reilly, account executive at Northwind, asked Memtro to log that BigCo had agreed pricing and to add a task to send the contract on Thursday. Memtro logged the activity on the deal and added the task. Nobody was emailed.
The teams that lean on Pipeline CRM most, a question each of them asks, and what they connect beside it.
A record in Pipeline CRM 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 Pipeline CRM, an account admin first allows you to manage API tokens. Then open Your profile → API tokens and create a token named Memtro.
Choose Read only if Memtro should only read, otherwise read-write, and copy the token, which is shown once. It acts as you.
In Memtro, open Connections → Pipeline CRM and paste it into API token. Fill in App key only if you are using a legacy api_key.
Ask your first question: which deals are expected to close this month?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Pipeline CRM tools are the same everywhere.
Only when you ask, and only what it has been granted: create a deal; change a deal's name, value, stage, probability, close date, company, people or owner (a stage or probability change can close the deal); delete a deal (permanent); create a person (lead or contact); change a person's name, email, position, company, status or owner; create a company; log an activity (note) on a deal, person or company; delete an activity (permanent); comment on an activity (users on its notify list are emailed); add a task or event to a deal, person or company; mark a task or event complete or not complete. 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 token, with an app key for a legacy api_key. In Pipeline CRM, an account admin first allows you to manage API tokens. Then open Your profile → API tokens and create a token named Memtro.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Pipeline CRM, choosing the same kinds; the tab shows Pipeline CRM'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