Briefing before a visit
Sarah Chen, major gifts officer at Acme Foundation, asked what a donor had given before meeting them. Memtro read the account's donations with their campaigns and funds, and named the membership level and its end date.
How much has this donor given, and to which campaigns?
Neon CRM holds your supporters and their giving, and Memtro reads it for your fundraising team. It reads accounts with membership status and source, and an account's donations, memberships, pledges and event registrations. It runs report-style searches of accounts, donations, activities and events, and reads events, campaigns, funds and other lookups. When asked and granted, it can update accounts, link contacts to companies, manage activities, create campaigns, delete donations, and refund or cancel payments. Neon can tell Memtro when a donation or account changes, and a job can start on it. Next Gen events are not in the API.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Neon CRM tool, reads what it needs, and answers with the source cited.
These tools change something in Neon CRM. 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 Neon CRM, choosing the same kinds; the tab shows Neon CRM's own steps. Each event can start a job, with the event as its input. Neon CRM sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Neon CRM 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 much has Northwind Trust given us this year?
Which donations over 500 came in since January?
Which memberships end next month?
Who has registered for the spring gala?
Log a call with Maya Okafor about her pledge.
Sarah Chen, major gifts officer at Acme Foundation, asked what a donor had given before meeting them. Memtro read the account's donations with their campaigns and funds, and named the membership level and its end date.
When Neon CRM told Memtro a donation was created, a job started for Tom Reilly, the supporter care lead. It read the donation's amount and campaign, and, as granted, created a thank-you call activity assigned to him.
The teams that lean on Neon CRM most, a question each of them asks, and what they connect beside it.
A record in Neon CRM 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 Neon CRM, copy the Organization ID from Settings, Organization Profile. Then in User Management open a dedicated user, turn on API Access and copy its key.
In Memtro, open Connections → Neon CRM and enter the Org ID and API key. Set Instance to trial only for a free-trial account.
The key has that user's permissions, so an administrator grants the account, activity and payment actions by name. Events are turned on from the connection's Events tab, then each webhook is added in Neon's Global Settings.
Ask how much a donor has given this year.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Neon CRM tools are the same everywhere.
Only when you ask, and only what it has been granted: update an account's name, title, department, email or no-solicitation flag; link an individual's contact to a company account; unlink an individual's contact from a company account; create an activity (task, call or meeting) on accounts; update an activity; delete an activity; create a fundraising campaign; delete a donation permanently; refund a Neon Pay payment or cancel an offline payment. 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.
Org ID and API key, plus instance. In Neon CRM, copy the Organization ID from Settings, Organization Profile. Then in User Management open a dedicated user, turn on API Access and copy its key.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Neon CRM, choosing the same kinds; the tab shows Neon CRM'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