LearnWorlds
Manage LearnWorlds courses, users, enrollments, tags and payments for your online school.
About
LearnWorlds ships in the w6w first-party pack. It declares 12 actions, 3 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.learnworlds- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Commerce & Payments
Overview
LearnWorlds is a per-school online course platform — each customer runs their own branded school on its own subdomain or custom domain — and this app puts the daily loop of running one behind a workflow: courses, users, enrollments, tags and payments.
Course catalog reads (list courses, get a course, get its sections and learning units) cover the read side. User management is the core of the write side: create and update users, and attach or detach tags to segment them for automations and reporting. Enrollment actions let a workflow list, add, or remove a user’s access to a course, bundle or subscription — the same action LearnWorlds’ own admin console performs when an instructor manually grants or revokes access. Payment history rounds it out, for reconciling a purchase against the enrollment or automation it should have triggered.
Authentication is OAuth2 client credentials, minted per school from Settings → Developers → API — available on the Learning Center and High Volume & Corporate plans. Health checks track LearnWorlds’ own status page alongside a live reachability probe of this connection’s specific school domain, since a suspended plan or a renamed subdomain is a different problem from a vendor-wide outage.
Deliberately out of scope for this first pass: course/bundle/subscription-plan creation beyond reading the catalog, promotions and coupons, affiliates, certificates, community spaces and posts, user groups and roles, seats, and webhooks — each is its own surface in LearnWorlds’ API, left for a future pass.
Build with LearnWorlds
Three routes to the same 12 actions. The Workflow tab is generated from LearnWorlds's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
List a User's Enrollments
user-enrollments-list List the products (courses, bundles, subscriptions) a user is enrolled in.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying LearnWorlds's real ids.
{
"manifestVersion": "2",
"name": "learnworlds-example",
"steps": [
{
"id": "course-contents-get",
"uses": {
"app": "io.w6w.learnworlds",
"action": "course-contents-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get Course Contents
readcourse-contents-get -
Get a Course
readcourse-get -
List Courses
searchcourses-list -
List Payments
searchpayments-list -
Create a User
performuser-create
+7 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for LearnWorlds, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to LearnWorlds. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "course-contents-get",
payload: {
id: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action course-contents-get --payload '{"id":"<value>"}'Give an AI agent LearnWorlds — without giving it LearnWorlds's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.learnworlds#course-contents-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's LearnWorlds connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
LearnWorlds's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. LearnWorlds itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
LearnWorlds declares its own checks, so its health is a property of the app rather than something the host guesses at.
LearnWorlds platform status
Component status from status.learnworlds.com. Covers the Video, Email and Course Hub services, Analytics, Account, Databases, Schools, and the Google Cloud/Cloudflare infrastructure LearnWorlds itself depends on.
School domain reachable
Unauthenticated request to this connection's school domain. A 400 'missing client_id' response passes — it proves the school is serving; credential validity is the `auth:*` check's job.
Rate-limit headroom
Not exposed: LearnWorlds documents a fixed 30 requests/10s limit and a 429 error shape, but no response header or endpoint reports remaining headroom.