Checking a weekend push
Maya Okafor, growth lead at Northwind, asks how Saturday's sale push did. Memtro finds the message and gives its delivered, clicked and errored counts. It then opens the message to show where the errors fell by platform.
How did our last push, email or SMS from OneSignal actually land?
OneSignal reads the push, email and SMS messages one app has sent or scheduled, with how many were delivered, clicked, errored or unsubscribed, and figures per platform. It also lists audience segments and message templates. One connection covers one app. When asked, and once an administrator has granted the action by name, it sends pushes, emails and SMS to segments or named users, cancels scheduled sends, manages segments and templates, broadcasts to every user's inbox and records custom events. Sends reach real people and cannot be recalled once delivered, and SMS spends credits. Deleting a user or template is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right OneSignal tool, reads what it needs, and answers with the source cited.
These tools change something in OneSignal. 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 OneSignal, choosing the same kinds; the tab shows OneSignal's own steps. Each event can start a job, with the event as its input. OneSignal sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce OneSignal 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 did last week's push do?
Which messages had the most errors this month?
Break down yesterday's sale push by platform
Which of our segments are read-only?
Schedule a push to the Lapsed users segment for 9am Saturday saying the sale ends Sunday
Maya Okafor, growth lead at Northwind, asks how Saturday's sale push did. Memtro finds the message and gives its delivered, clicked and errored counts. It then opens the message to show where the errors fell by platform.
Tom Reilly, CRM manager at Acme Ltd, asks Memtro to remind lapsed users that the sale ends on Sunday. He approves the text, audience and time, and Memtro schedules the push to the Lapsed users segment for Saturday morning. OneSignal delivers it to every subscribed device in the segment.
The teams that lean on OneSignal most, a question each of them asks, and what they connect beside it.
A record in OneSignal 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 OneSignal, open your app, then Settings → Keys & IDs, and copy the App ID from the top of the page.
On the same page, choose Add Key, name it Memtro, leave the IP allowlist empty, and copy the key, which is shown once. The key reaches the whole app, sending included, so Memtro sends only what an administrator grants.
In Memtro, open Connections → OneSignal and paste the App ID and the App API key.
Ask "How did last week's push do?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The OneSignal tools are the same everywhere.
Only when you ask, and only what it has been granted: send a push notification to segments or named users (notifies them); send an email to segments, named users or addresses (notifies them); send an SMS to segments, named users or phone numbers (notifies them, spends SMS credits); cancel a scheduled or sending message; create a segment from filters; delete a segment; create a push, email or SMS template; edit a template (changes anything sending from it); delete a template (permanent); broadcast a message to every user's in-app inbox; record custom events against users (may trigger journeys); delete a user with their properties and subscriptions (permanent); copy a journey as a new draft. 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 OneSignal records into memory as entities.
App ID and App API key. In OneSignal, open your app, then Settings → Keys & IDs, and copy the App ID from the top of the page.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in OneSignal, choosing the same kinds; the tab shows OneSignal'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