How many people enrolled in our course this month, and what did it earn?
Teachable shows how your online school is doing. You see courses with their sections and lectures, enrollments per course with completion counts and average progress, users, sales transactions with refunds and chargebacks, and pricing plans. When asked and granted, Memtro can add or rename users, enroll or unenroll a user in a course, and mark a lecture complete for someone. Teachable can tell Memtro when a user enrolls, completes a course or makes a purchase, and a job can start on it, once you add the address in Teachable. The API needs the Growth plan or higher.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Teachable tool, reads what it needs, and answers with the source cited.
These tools change something in Teachable. 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 Teachable, choosing the same kinds; the tab shows Teachable's own steps. Each event can start a job, with the event as its input, and can be remembered where you choose. Teachable signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Teachable 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.
Teachable + MemtroHow many people enrolled in the Excel Basics course this month?
What revenue did sales bring in last week?
Which transactions were refunded this month?
What lectures are in the Getting Started section?
Enroll Tom Reilly in the Onboarding course.
Maya Okafor, course director at Acme Ltd's academy, asked how many people enrolled in Excel Basics this month. Memtro counted the active enrollments dated this month and gave the course's completion count and average progress.
At Northwind, a job starts when Teachable sends a new sale. Memtro reads the transaction and the buyer's enrollments, then, as granted, enrolls them free in the onboarding course, and Teachable may send them its welcome email.
The teams that lean on Teachable most, a question each of them asks, and what they connect beside it.
A record in Teachable 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
Kajabi
Kontent.ai
WufooIn your Teachable school admin, the school owner opens Settings, then API, and creates a key. The API needs the Growth plan or higher.
In Memtro, open Connections → Teachable and paste it into API key.
An administrator grants the actions by name, such as Enroll user or Unenroll user, to the teams that may use them.
Ask how many people enrolled in a course this month. Events are turned on from the connection's Events tab, and the address is then added under Settings, then Webhooks, in Teachable.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Teachable tools are the same everywhere.
Only when you ask, and only what it has been granted: add a user to the school; change a user's name or signup source; enroll a user in a course (free); unenroll a user from a course; mark a lecture complete for a user. 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.
API key. In your Teachable school admin, the school owner opens Settings, then API, and creates a key. The API needs the Growth plan or higher.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Teachable, choosing the same kinds; the tab shows Teachable'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
