Who joined which GetResponse list, how they signed up and which segment they sit in.
Connect GetResponse with an API key and Memtro reads your lists (GetResponse calls them campaigns), contacts with their list, origin, score and sign-up date, saved segments with the contacts in them, and tags. 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 subscribe, change, tag or permanently delete contacts, create lists and tags, fire custom events, and draft, send, schedule or cancel newsletters and transactional emails. Sending emails people outside the company, counts against the plan's limits and cannot be recalled once delivered.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right GetResponse tool, reads what it needs, and answers with the source cited.
These tools change something in GetResponse. 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 GetResponse, choosing the same kinds; the tab shows GetResponse's own steps. Each event can start a job, with the event as its input. GetResponse signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce GetResponse 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.
GetResponse + MemtroHow many contacts joined the newsletter list this month?
Which list is dan@northwind.com on, and when did he sign up?
Who is in the Webinar attendees segment?
Which contacts have the highest score on the customers list?
Cancel the newsletter scheduled for Friday
The marketing lead asks how many people joined the newsletter list in October and how they signed up. Memtro reads the contacts newest first, counts them by origin, and names the highest-scoring sign-ups so sales can look at them first.
Priya Sharma spots a wrong price in the newsletter scheduled for Friday and asks Memtro to stop it. Memtro cancels the scheduled newsletter, which GetResponse turns back into a draft, and nobody on the lists is emailed.
The teams that lean on GetResponse most, a question each of them asks, and what they connect beside it.
A record in GetResponse 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.
ActiveCampaign
Klaviyo
MailerLite
Instantly
lemlist
Drip
Omnisend
Mailjet
Moosend
Smartlead
Iterable
Dotdigital
Flodesk
LoyaltyLion
Benchmark Email
Braze
Sender
Rewardful
Mailshake
SurveySparrow
RetentlyIn app.getresponse.com open Integrations → API, generate an API key and copy it, noting a key unused for 90 days expires and has to be replaced
On GetResponse MAX only, also enter the MAX account domain alone (no https://) and the MAX region, US or PL, and leave both blank for an ordinary account
In Memtro open Connections → GetResponse, paste the API key and connect
Ask how many contacts joined each list this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The GetResponse tools are the same everywhere.
Only when you ask, and only what it has been granted: create a tag (on no contact, so it starts no automation); subscribe a person to a list; change a contact's details, list or tags; add tags to a contact; delete a contact; save a newsletter as a draft; send or schedule a newsletter to lists or segments; send a saved newsletter draft; cancel a queued or scheduled newsletter; send a transactional email to up to 8 people; fire a custom event for a contact; create a list; delete a tag. 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.getresponse.com open Integrations → API, generate an API key and copy it, noting a key unused for 90 days expires and has to be replaced.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in GetResponse, choosing the same kinds; the tab shows GetResponse'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