Monday replies
On Monday the growth lead asks who replied last week. Memtro reads lemlist's activity for the last seven days and lists each reply with the lead, their company and the campaign, so follow-ups go to the warmest leads first.
Which leads replied to a lemlist campaign, and how each campaign is doing.
Connect lemlist with an API key, and Memtro reads campaigns with status, the leads in a campaign, campaign activity by lead and date, campaign totals for a period, and contacts. 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 send an email, add leads to campaigns, create, pause, resume or archive campaigns, mark, pause or unsubscribe leads, add notes and tasks, and permanently delete a contact. Emails and running campaigns reach people outside the company and cannot be recalled.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right lemlist tool, reads what it needs, and answers with the source cited.
These tools change something in lemlist. 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 lemlist for you. Each event can start a job, with the event as its input. lemlist sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce lemlist 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.
Who replied to our campaigns this week?
How did the Q4 founders campaign do over the last 30 days?
Which campaigns are paused or have errors?
Which leads bounced in the Northwind outreach campaign?
Pause the Northwind outreach campaign until Monday
On Monday the growth lead asks who replied last week. Memtro reads lemlist's activity for the last seven days and lists each reply with the lead, their company and the campaign, so follow-ups go to the warmest leads first.
Priya Sharma at Brightwave Ltd replies that she is interested but busy until spring. The account lead asks Memtro to mark her interested and pause her. Memtro does both in lemlist, so no further steps reach her until she is resumed.
The teams that lean on lemlist most, a question each of them asks, and what they connect beside it.
A record in lemlist 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 app.lemlist.com open your profile picture (bottom left) → Settings → Integrations and generate a new API key
Copy it straight away, as lemlist shows it once
In Memtro open Connections → lemlist, paste the API key and connect
Ask who replied this week, noting a contact note is also pushed to the team's connected CRM, if there is one
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The lemlist tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a contact; add a note to a company; create a manual task on a contact, company or lead; add a lead to a lemlist campaign; send an email to a contact from a lemlist inbox; create a lemlist campaign; pause a lemlist campaign; resume a paused lemlist campaign; archive a lemlist campaign; mark a lemlist lead as interested or not interested; pause or resume a lemlist lead; unsubscribe a lead from a lemlist campaign; delete a lemlist contact and everything attached to it. 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 app.lemlist.com open your profile picture (bottom left) → Settings → Integrations and generate a new API key.
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 lemlist 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