Who bought the coaching offer this month?
Kajabi connects Memtro to your creator platform. It reads contacts by name, email, tag, offer or subscription, their notes and tags, and the offers you sell with their prices. It also reads purchases, payment transactions, forms and sites. When asked and granted, it can create, update or delete contacts, manage notes and tags, grant or revoke offers, submit a form, and deactivate, reactivate or cancel the subscription behind a purchase. Tags and forms can start the site's automations, which may email people. Phone numbers, addresses, card holder names and billing details are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kajabi tool, reads what it needs, and answers with the source cited.
These tools change something in Kajabi. 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 Kajabi 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.
Kajabi + MemtroWho bought the coaching offer this month?
Which contacts carry the VIP tag?
What refunds went through last month?
What offers do we sell, and at what price?
Add a note to Sarah Chen's contact saying she prefers morning calls.
Tom Reilly, founder of the coaching practice at Northwind, asked who bought the coaching offer this month. Memtro read the purchases for that offer and matched them to contacts. He had his list of new clients without exporting anything.
Priya Sharma, community manager at Acme Ltd, asked Memtro to grant the masterclass offer to a guest speaker without a welcome email. With the action granted, Memtro granted it with the welcome turned off. The speaker had access and Kajabi sent nothing.
The teams that lean on Kajabi most, a question each of them asks, and what they connect beside it.
A record in Kajabi 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.
Jotform
DataForSEO
Moz API
Hygraph
Paperform
Kontent.ai
Teachable
WufooIn Kajabi admin, open Settings → Security → User API Keys and create a key named Memtro. View permissions cover the reads, and each change needs its matching permission.
In Memtro, open Connections → Kajabi and paste the Client ID and Client secret.
An administrator grants the actions by name, such as Grant an offer to a contact, to the teams that may use them.
Ask "Who bought the coaching offer this month?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kajabi tools are the same everywhere.
Only when you ask, and only what it has been granted: create a contact on a site; update a contact; delete a contact; add a note to a contact; edit a contact note; delete a contact note; add tags to a contact (may start automations); remove tags from a contact; grant an offer to a contact (emails a welcome unless told not to); revoke an offer from a contact; submit a form for a person (may send an opt-in email and start automations); deactivate a purchase (removes access); reactivate a purchase; cancel the subscription behind a purchase. 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.
Client ID and client secret. In Kajabi admin, open Settings → Security → User API Keys and create a key named Memtro. View permissions cover the reads, and each change needs its matching permission.
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
