Morning reply check
The sales lead asks which leads replied to the Q4 outreach campaign overnight. Memtro searches the campaign's leads by replied status and lists six, each with company, sequence step and the first line of the latest reply.
Ask Smartlead which leads replied to a campaign, and how each mailbox is warming up.
Connect Smartlead with an API key and Memtro reads campaigns each campaign's sent, open, reply and bounce figures, leads with sequence step and latest reply, and sending mailboxes with warmup health. Mailbox passwords are never returned. The hourly sync writes campaign leads into memory. When asked, and once an administrator has granted the action by name, it can create and start, pause or stop campaigns, add leads, reply to a lead, and resume paused leads. Starting, adding to a running campaign, resuming and replying all send real email to people outside the company. Unsubscribing a lead is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Smartlead tool, reads what it needs, and answers with the source cited.
These tools change something in Smartlead. 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 Smartlead, choosing the same kinds; the tab shows Smartlead's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Smartlead signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Smartlead 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 replied to the Q4 Northwind campaign?
What is the reply rate on our active campaigns?
Which mailboxes have poor warmup reputation?
Which leads in the BigCo campaign bounced?
Reply to Priya Sharma that Thursday at 2pm works for a call
The sales lead asks which leads replied to the Q4 outreach campaign overnight. Memtro searches the campaign's leads by replied status and lists six, each with company, sequence step and the first line of the latest reply.
Tom Ellis asks Memtro to tell Priya Sharma at Globex that Thursday at 2pm works, and to mark her as Meeting Booked. Memtro sends his approved words as a reply in her thread from the campaign mailbox and sets the category, and Priya receives the email.
The teams that lean on Smartlead most, a question each of them asks, and what they connect beside it.
A record in Smartlead 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.smartlead.ai open Profile → Settings → API Keys and choose Generate New API Key, then copy it, as Smartlead shows it once
Use the main account's key: an agency client's key is refused by lead search
Paste the API key into Connections → Smartlead in Memtro and connect
Ask which leads replied to your newest campaign
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Smartlead tools are the same everywhere.
Only when you ask, and only what it has been granted: add a note to a campaign lead; create a task on a campaign lead; create a draft campaign; start, pause, stop or archive a campaign; add leads to a campaign; reply to a lead in their email thread; update a lead's details in a campaign; set or clear a lead's category; pause a lead in a campaign; resume a paused lead; mark a lead complete in a campaign; unsubscribe a lead; remove a lead from a campaign. 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 Smartlead records into memory as entities.
API key. In app.smartlead.ai open Profile → Settings → API Keys and choose Generate New API Key, then copy it, as Smartlead shows it once.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Smartlead, choosing the same kinds; the tab shows Smartlead'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