Your Copper pipeline, people and tasks, and every deal change remembered.
Connect Copper with an API key and its user's email, and Memtro reads pipelines and stages, opportunities by stage, status and owner with their values, people, companies, leads, activities and tasks. Every hour it writes each opportunity that changed into memory as a deal. When you ask, and once an administrator has granted each action by name, it can add notes, create and move opportunities, create and complete tasks, add people, leads and companies, and convert a lead, all under the key's user. Converting a lead removes it, and deleting an opportunity, task or person is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Copper tool, reads what it needs, and answers with the source cited.
These tools change something in Copper. 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 Copper for you. Each event can start a job, with the event as its input. Copper sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Copper 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.
Copper + MemtroWhich opportunities in the Sales pipeline are at Proposal and who owns them?
What did we win in October and what was it worth?
What happened with Northwind Traders in the last two weeks?
Mark the Bluefin renewal as Won
Add a note to the Bluefin renewal opportunity: they want the contract by 20 November
On Monday the sales lead asks what moved last week. Memtro lists the opportunities that changed stage, the two that were won with their values, and the leads still unconverted, drawn from the hourly sync and a fresh read of Copper.
Sam Reyes finishes a call with Northwind Traders and asks Memtro to move their opportunity to Negotiation, note that they want a 12-month term, and set him a task to send the contract on Thursday. Memtro makes all three changes in Copper under the key's user, where everyone with access to the pipeline sees them.
The teams that lean on Copper most, a question each of them asks, and what they connect beside it.
A record in Copper 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
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
Affinity
Kommo
Pipeline CRM
KeapIn Copper open Settings → Integrations → API Keys, generate an API key and note which user generated it: Copper only accepts the key together with that user's email
In Memtro open Connections → Copper, paste the API key and the Email of the key's user, and connect. The key reads and writes whatever that user can see
Memtro only reads until an administrator grants an action by name, such as adding notes or moving opportunities. Copper allows 180 requests a minute
Ask what moved in the Sales pipeline this week, or what is overdue for Priya
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Copper tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a person, company, opportunity or lead; create an opportunity, or change its stage, status, value, owner or details; create a task, or update or complete one; create a person, or update their name, title, emails, phones or owner; create a lead or a company; convert a lead into a person, with a company and an opportunity if asked (the lead is removed); delete an opportunity, task or person permanently. 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 Copper records into memory as entities.
API key and Email of the key's user. In Copper open Settings → Integrations → API Keys, generate an API key and note which user generated it: Copper only accepts the key together with that user's email.
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 Copper 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