What went out
The ecommerce lead at Brightwave Ltd asks what Omnisend sent this month. Memtro lists six campaigns newest first, four emails, one SMS and one push, each with its status, start and end dates and a link to its report.
Ask which Omnisend campaigns went out this month, and which automations are switched on.
Connect Omnisend with an API key and Memtro reads contacts with tags and subscription state, email, SMS and push campaigns, segments, templates and automations. Phone, address and birthdate are never read. The hourly sync writes each contact that changed into memory. When you ask, and once an administrator has granted the action by name, it can draft, test, schedule, cancel and send campaigns, create and update contacts and tags, and switch automations on or off. Sending reaches customers and cannot be recalled, and subscribing or tagging can start automations that message them. Deleting a campaign or segment is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Omnisend tool, reads what it needs, and answers with the source cited.
These tools change something in Omnisend. 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.
Once Omnisend 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 campaigns went out this month, and on which channel?
Which automations are switched on right now?
Is priya.sharma@brightwave.co.uk subscribed to email and SMS?
Which contacts are tagged VIP?
Draft the winter sale email to the VIP segment and send me a test
The ecommerce lead at Brightwave Ltd asks what Omnisend sent this month. Memtro lists six campaigns newest first, four emails, one SMS and one push, each with its status, start and end dates and a link to its report.
Support hears that new customers got no welcome email. Memtro finds the welcome automation was disabled on 3 November and, when Laura Chen asks, enables it again. Omnisend starts sending the welcome email to new subscribers as they sign up.
The teams that lean on Omnisend most, a question each of them asks, and what they connect beside it.
A record in Omnisend 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.omnisend.com open Integrations → API keys and create a key. If it can be limited, give it read access to contacts, campaigns, segments, automations and brands, and write access only to what Memtro should change
Copy the key at once: Omnisend shows it only once
In Memtro open Connections → Omnisend, paste the API key and connect
Ask which campaigns went out this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Omnisend tools are the same everywhere.
Only when you ask, and only what it has been granted: create an email or SMS campaign as a draft, edit a draft, or copy a campaign (sends nothing); email a test of a draft campaign to up to five addresses; send a draft campaign to its audience now or at its scheduled time; cancel a scheduled or sending campaign, or put a scheduled one back to draft; delete a campaign (permanent); create or update a contact, choosing their email subscription status (a welcome message only when asked); add or remove tags on named contacts (tags can start automations); enable or disable an automation (enabling starts messaging contacts); delete a segment (permanent). 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 Omnisend records into memory as entities.
API key. In app.omnisend.com open Integrations → API keys and create a key. If it can be limited, give it read access to contacts, campaigns, segments, automations and brands, and write access only to what Memtro should change.
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