Before a sales call
The account manager asks what Mautic knows about Priya Nair at Brightwave Ltd. Memtro returns her points, stage, tags and the last three notes, including a call logged on 4 November.
Ask which campaigns and segments a contact is in, and what Mautic emails went out.
Connect your self-hosted Mautic with an API credential, or a username and password, and Memtro reads contacts with notes, points and tags, companies, campaigns, emails with sent and read counts, and segments. Phone numbers, addresses and IP addresses are never read. When you ask, and once an administrator has granted them by name, it can manage contacts, companies, segments and emails, mark do not contact, and send an email to one contact or to whole segments, possibly thousands of people. Publishing a campaign or adding someone to it can email contacts automatically. Deletes are permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Mautic tool, reads what it needs, and answers with the source cited.
These tools change something in Mautic. 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 Mautic for you. Each event can start a job, with the event as its input. Mautic signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Mautic 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 segments is priya@brightwave.example in?
Which emails went out last month, and how many were read?
Who are our highest-scoring contacts at Acme?
Mark dan@northwind.example as do not contact
Send the webinar reminder email to the Acme trial segment
The account manager asks what Mautic knows about Priya Nair at Brightwave Ltd. Memtro returns her points, stage, tags and the last three notes, including a call logged on 4 November.
Support receives a request from a Northwind contact to stop marketing email, and Sarah Collins asks Memtro to act on it. With the action granted, Memtro marks the contact do not contact for email, so Mautic sends them nothing more, and keeps the record rather than deleting it.
The teams that lean on Mautic most, a question each of them asks, and what they connect beside it.
A record in Mautic 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.
An administrator must enable the API under Settings (cog) → Configuration → API Settings, and HTTP basic auth too if you use a username and password
Create an OAuth 2 API credential (Mautic 5) or a dedicated user whose role has only the permissions Memtro needs. A role without email send permission keeps sending out of reach
In Connections → Mautic in Memtro type the Host name only, with the API at its root and a publicly trusted certificate, no https:// or path, then the API client ID and secret, or the username and password
Ask which campaigns a contact is in
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Mautic tools are the same everywhere.
Only when you ask, and only what it has been granted: create a contact (Mautic may update an existing contact with the same email); update fields or tags of a contact; delete a contact; mark a contact as do not contact for email; create a company; create an unpublished, empty campaign; add a note to a contact; create a segment; add a contact to a segment (campaigns from it may email them); remove a contact from a segment; send an email to one contact; send a segment email to every contact in its segments; create an email (unpublished unless asked; sends nothing); edit an email's name, subject, content, sender, segments or published state; delete an email; publish or unpublish a campaign (a published campaign acts on, and may email, its contacts); delete a campaign; add a contact to a campaign (its actions may email them); remove a contact from a campaign; rename a segment or change its description or published state; delete a segment; update a company's fields; delete a company; link a contact to a company, or unlink them; lift do-not-contact for email from a contact; add or subtract points on a contact. 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.
Host and API credential, or user and password. An administrator must enable the API under Settings (cog) → Configuration → API Settings, and HTTP basic auth too if you use a username and password.
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 Mautic 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