Unhealthy mailboxes
Replies have dropped, and the outbound lead asks which mailboxes are unhealthy. Memtro reads the sending accounts and lists those with a poor warmup status or score, each with its daily limit, so the weak ones are paused first.
How each Instantly campaign is doing, who replied, and which mailboxes are unhealthy.
Connect Instantly with a v2 API key, and Memtro reads campaigns with status and daily limit, campaign analytics, leads with interest and engagement, sent and received emails, sending accounts with warmup score, and lead lists. An hourly sync writes sent and received emails into memory. When you ask, and once an administrator has granted the action by name, it can start, pause or duplicate campaigns, reply to emails, add, edit, move or permanently delete leads, and pause sending accounts. Starting a campaign, adding leads to a running one, and replying all email 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 Instantly tool, reads what it needs, and answers with the source cited.
These tools change something in Instantly. 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 Instantly for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Instantly sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Instantly 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.
How is the Q4 campaign doing?
Which leads replied and are marked interested?
Which mailboxes have a low warmup score?
What did Dan Fletcher at Acme reply to our last email?
Pause the Northwind outreach campaign
Replies have dropped, and the outbound lead asks which mailboxes are unhealthy. Memtro reads the sending accounts and lists those with a poor warmup status or score, each with its daily limit, so the weak ones are paused first.
Dan Fletcher at Acme replies asking for pricing, and Priya Sharma asks Memtro to answer. Memtro shows the reply, and once she approves the words, sends it from the same sending account to Dan, and the thread continues in Instantly.
The teams that lean on Instantly most, a question each of them asks, and what they connect beside it.
A record in Instantly 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.
Instantly's API needs a paid Instantly plan, and a workspace without one is refused
In Instantly open Settings → Integrations → API keys and create a v2 key with all:read, adding scopes such as campaigns:update, leads:create or emails:create only for the actions you want Memtro to take, since a v1 key will not work
In Memtro open Connections → Instantly, paste the API key and connect
Ask how your campaigns did this month, noting the email list allows only 20 calls a minute
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Instantly tools are the same everywhere.
Only when you ask, and only what it has been granted: create an empty lead list; start or resume a campaign: it begins emailing its leads; pause a campaign; duplicate a campaign (the copy is not started); reply to a received email from a connected sending account; add one lead, or up to 100, to a campaign (they will be emailed) or a list; edit a lead's fields or interest status; set a lead's interest status by email address; move or copy named leads to another campaign or list; delete a lead permanently; pause or resume a sending account; mark an email thread read. 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 Instantly records into memory as entities.
API key (v2). Instantly's API needs a paid Instantly plan, and a workspace without one is refused.
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 Instantly 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