Reviewing the Spring campaign
Sarah Chen, head of growth at Northwind, asked how the Spring campaign did. Memtro returned its sends, opens, clicks, unsubscribes and bounces from Loops. She took the figures straight into the Monday review.
Is this person subscribed, and how did our last campaign do?
Loops finds a contact by email or user id, with whether they are subscribed, their opt-in status and mailing lists. It reads campaigns with their status, audience and all-time sends, opens, clicks and bounces, and transactional emails with their delivery figures. It also lists mailing lists, segments and contact properties. When asked and granted, it can add, change or permanently delete contacts, send a transactional email or a test preview, send or schedule a campaign to its whole audience, record events that may start workflows, and create and edit drafts. Sent email cannot be recalled.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Loops tool, reads what it needs, and answers with the source cited.
These tools change something in Loops. 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 Loops, choosing the same kinds; the tab shows Loops's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Loops signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Loops 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.
Is priya@globex.com subscribed?
How did the Spring campaign do?
Which campaigns are scheduled?
What data does the password reset email expect?
Send the password reset email to dan@acme.com
Sarah Chen, head of growth at Northwind, asked how the Spring campaign did. Memtro returned its sends, opens, clicks, unsubscribes and bounces from Loops. She took the figures straight into the Monday review.
Dan Fletcher, account manager at Acme Ltd, asked Memtro to send a test preview of the renewal campaign to himself and Tom Reilly. Memtro sent the preview to those two addresses only, and after reading it Dan asked for the campaign to be scheduled for Monday.
The teams that lean on Loops most, a question each of them asks, and what they connect beside it.
A record in Loops 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 Loops, open Settings → API and choose Generate key.
Copy the key, as Loops shows it once. It has no scopes and carries the whole team's access, so consider a key kept for Memtro alone.
In Memtro, open Connections → Loops and paste it into API key.
Ask "Is priya@globex.com subscribed?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Loops tools are the same everywhere.
Only when you ask, and only what it has been granted: add a contact (unsubscribed unless asked, never overwriting an existing one); create a campaign as a draft (never scheduled or sent); update a contact's name, group, subscription or mailing lists (creates the contact if none matches); delete a contact (permanent); lift a contact's suppression so they can be emailed again; send a transactional email to one address (the recipient is emailed); send an event for a contact (workflows listening for it may email them); rename a campaign or change its audience; send a campaign now or schedule it (its whole audience is emailed); edit the subject, sender or body of a draft campaign or transactional email; send a test preview of an email to listed addresses; create a transactional email (an empty draft); publish a transactional email's draft so it can be sent; create a custom contact property; create a draft workflow. 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 Loops, open Settings → API and choose Generate key.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Loops, choosing the same kinds; the tab shows Loops'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