Appeal progress check
Sarah Chen, fundraising manager at Northwind, asked how the winter appeal was doing. Memtro read the campaign's goal and amount raised, and listed the fundraising pages that had raised the most.
How far is our appeal from its goal, and which regular gifts are failing?
Raisely shows you campaigns with goals and totals, donations by campaign, page, supporter or status, and supporters. It reads fundraising pages with totals and donor counts, regular gifts, interactions, interaction categories and tags. When asked and granted, it can create or update supporters, log interactions, and tag or untag records. It can also record, edit or delete offline donations, and email donation receipts. Raisely can tell Memtro as it happens when a donation is made or a regular gift fails, and a job can start on it. Memtro never reads supporters' emails, phone numbers, addresses or card details.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Raisely tool, reads what it needs, and answers with the source cited.
These tools change something in Raisely. 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 Raisely for you. Each event can start a job, with the event as its input, and can be remembered where you choose. Raisely sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Raisely 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 far is the spring appeal from its goal?
Which regular gifts are failing?
Which fundraising pages have raised the most on the fun run?
What donations came in yesterday?
What interactions have we logged with this supporter?
Sarah Chen, fundraising manager at Northwind, asked how the winter appeal was doing. Memtro read the campaign's goal and amount raised, and listed the fundraising pages that had raised the most.
When a regular gift's charge started failing in Raisely, a job started for Dan Fletcher, supporter care lead at Acme Ltd. It read the gift and the supporter's interactions and, with the action granted, logged a note asking the team to call.
The teams that lean on Raisely most, a question each of them asks, and what they connect beside it.
A record in Raisely 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 the Raisely campaign admin open Settings, then Developers, and copy the campaign private key. It has administrator access to the campaign, with no scopes.
In Memtro open Connections → Raisely and paste the Campaign private key.
An administrator grants the donation, receipt and supporter actions by name to the teams that may use them. Events are turned on from the connection's Events tab.
Ask: how far is the spring appeal from its goal?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Raisely tools are the same everywhere.
Only when you ask, and only what it has been granted: create a supporter, or update the one with that email; update a supporter; log an interaction on a supporter; tag records; remove a tag from a record; record an offline donation; edit a donation's donor details or message; delete an offline donation; email a donation receipt to the donor. 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.
Campaign private key. In the Raisely campaign admin open Settings, then Developers, and copy the campaign private key. It has administrator access to the campaign, with no scopes.
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 Raisely 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