Pipeline review
Sarah Chen, sales manager at Acme Ltd, asked which leads had sat in negotiation longest. Memtro listed them with sale value, responsible user and last update, and named two with no next task.
Which Kommo leads are stuck in negotiation, and who owns them?
Kommo, formerly amoCRM, connects Memtro to your sales. It reads leads with sale value, pipeline, stage, responsible user, dates, tags and linked contacts and companies, contacts with their primary email and phone, companies, pipelines and their stages, tasks with deadlines and the account's users. When asked, and once an administrator has granted the action by name, it can create and update leads, including moving one to another stage, which may run that stage's automations, create and update contacts and companies, add a note, and create, change or complete a task. Note text, chats and other custom fields are never read.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kommo tool, reads what it needs, and answers with the source cited.
These tools change something in Kommo. 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 Kommo 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 leads are in negotiation this week?
What is the total value of leads in the main pipeline?
Which of my tasks are overdue?
Who is responsible for the BigCo lead?
Move the Northwind lead to Contract sent
Sarah Chen, sales manager at Acme Ltd, asked which leads had sat in negotiation longest. Memtro listed them with sale value, responsible user and last update, and named two with no next task.
Dan Fletcher, account executive at Northwind, asked Memtro to move the BigCo lead to contract sent and set a follow-up task for Friday. Memtro moved the lead, which ran any automation the account has on that stage, and created the task for Dan.
The teams that lean on Kommo most, a question each of them asks, and what they connect beside it.
A record in Kommo 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 Kommo, as an account administrator, open Settings → Integrations → Create integration → Private integration and create it.
Open it, go to the Keys and scopes tab, click Generate long-lived token, choose an expiry and copy the token, which is shown once and carries your rights.
In Memtro, open Connections → Kommo and paste your Account subdomain (acme for acme.kommo.com) and the Long-lived token. Only accounts on kommo.com are supported.
Ask your first question: which leads are in negotiation this week?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kommo tools are the same everywhere.
Only when you ask, and only what it has been granted: create a lead, optionally in a given pipeline and stage and linked to contacts and a company (stage automations may run); update a lead: rename it, set its value, move it to another stage or pipeline, reassign it, or add and remove tags (stage automations may run); create a contact, optionally with an email and phone; update a contact's name, responsible user or tags; create a company; update a company's name, responsible user or tags; add a note to a lead, contact or company; create a task on a lead, contact or company; change a task's text, deadline or responsible user; complete a task with a result. 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 Kommo records into memory as entities.
Account subdomain and Long-lived token. In Kommo, as an account administrator, open Settings → Integrations → Create integration → Private integration and create it.
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