LearnWorlds
CMS & ContentConnect AI agents to your LearnWorlds school. Agents create and update learners, enroll and unenroll them in courses and bundles, track course progress, browse the catalog, and reconcile payment transactions through the Admin REST API v2.
What This Integration Enables
A LearnWorlds school run by a small team fails in a predictable place: not the teaching, the administration. Access grants pile up without records, refunds require remembering to revoke, and progress data sits unused because exporting it is a chore. This connector puts the Admin REST API v2 under FlowRunner's control so agents run that administration continuously: creating and updating learners, enrolling and unenrolling across courses and bundles, tracking per-course progress, and reconciling payment transactions outward. The detail worth noticing is that LearnWorlds made manual enrollment carry a required justification note. That is governance thinking, and it matches how FlowRunner treats automation generally: every action should carry its reason. Agents fill that note with the order reference, the campaign name, or the support ticket, so the school's access ledger explains itself. - Buyers from Stripe, storefronts, or CRMs become learners with access, welcome email, and audit note in one flow - Promotional and partner access is granted at scale with the justification recorded per enrollment - Progress and completion per learner feed reporting, re-engagement, and certificate workflows - Payments export to accounting on a schedule, and manual grants never pollute revenue data because they create no payment record - Profile fixes, email corrections, and suspensions execute through Update User with only the provided fields touched Granting access is cheap to reverse; revoking it from a paying learner is not. FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate sits on the revoke.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The purchase that becomes a classroom seat in one minute
A payment clears in [Stripe](/integrations/stripe). The agent checks List Users by email, creates the learner if new, and calls Enroll User for the purchased course with the Stripe charge ID in the justification note. The instructor team sees the enrollment in [Slack](/integrations/slack), and the learner lands in the course onboarding audience in [Mailchimp](/integrations/mailchimp). When the school runs a partner promotion, the same flow enrolls the partner's list into the bundle, each grant annotated with the campaign name, so the comp cohort is identifiable forever.
Progress data that runs the re-engagement machine
Weekly, the agent walks List Users page by page and calls Get User Courses for active learners, logging completion percentage and status per course to [Google Sheets](/integrations/google-sheets). Learners stalled below threshold for two consecutive weeks get tagged into a win-back email sequence; completions trigger the certificate flow and a review request. The instructor sees a digest of who is stuck where. The data always existed inside the school; now it leaves the building and does work.
Revenue that reconciles itself
Nightly, the agent pulls List Payments for the day, amount, currency, user, product, timestamp, and appends the transactions to the accounting workbook. Because Enroll User grants never create payment records, the revenue data stays clean: comps are visible in the enrollment audit trail, not muddled into transactions. Month-end closes against a ledger that was already reconciled every night, and the founder answers "how did the course sell this month" from data instead of vibes.
Human-in-Loop Highlight
Unenroll User revokes a learner's access to a course or bundle immediately, and pointed at the wrong account it locks a paying customer out of the product mid-lesson, over a refund that was partial, a subscription webhook that fired out of order, or an email match that hit the wrong user. Update User carries the harsher version: suspension cuts off the whole account. So FlowRunner treats revocation as evidence-plus-approval: the agent assembles the refund or lapse record, the learner's profile from Get User, and their progress from Get User Courses, then presents the case to the school owner. A person confirms, grants grace, or spots the mismatch. Enrollments, account creation, and profile updates run autonomously because their failure modes are recoverable. Taking access away from someone who paid for it is the one operation on this connector where being fast matters less than being right.
Agent Capabilities
10 actionsUsers
4- List Users Retrieves a paginated list of users (learners) registered in your LearnWorlds school. Supports pagination via page number and page size. Returns core profile fields such as id, email, and username for each user. Use this to browse or export your school's audience.
- Get User Retrieves the full profile of a single user by their LearnWorlds user ID. Returns detailed fields including email, username, tags, subscription status, and account metadata. Use this to look up an individual learner's account details.
- Create User Creates a new user (learner) account in your LearnWorlds school. Requires an email address; a username and other optional profile fields can be supplied. Newly created users can then be enrolled in courses or bundles. Returns the created user's ID and profile.
- Update User Updates an existing user's profile fields by user ID. Only the fields you provide are changed; omitted fields are left untouched. Use this to correct an email/username, suspend or reactivate access, or adjust profile metadata.
Courses
2- List Courses Retrieves a paginated list of courses in your LearnWorlds school. Returns each course's id, title, and publication status. Use this to discover course IDs for enrollment operations or to sync your catalog.
- Get Course Retrieves the full details of a single course by its course ID, including title, description, access type (free/paid), pricing, and section/unit structure metadata. Use this to inspect a specific course before enrolling users.
Enrollment
3- Enroll User Enrolls a user in a specific course or bundle, granting them access to the product. Choose the product type (Course or Bundle) and provide the product ID. A justification note is required to record why the manual enrollment was granted (e.g. "Promotional access"). Use this to grant access without a purchase.
- Unenroll User Removes a user's enrollment from a specific course or bundle, revoking their access to that product. Choose the product type (Course or Bundle) and provide the product ID. Use this to reverse a manual enrollment or revoke access.
- Get User Courses Lists the courses a specific user is enrolled in, along with their progress in each course (such as completion percentage and status). Use this to track a learner's progress or verify what they currently have access to.
Payments
1- List Payments Retrieves a paginated list of payments (transactions) recorded in your LearnWorlds school. Returns each payment's amount, currency, associated user, product, and timestamp. Use this to reconcile revenue or sync transactions to another system.
Frequently Asked Questions
What can FlowRunner do with LearnWorlds?
FlowRunner agents can run List Users, Get User, and Create User in LearnWorlds, plus 7 more actions.
Does connecting LearnWorlds to FlowRunner require OAuth?
No. LearnWorlds connects to FlowRunner with an API key, no OAuth flow required.
Can LearnWorlds trigger a FlowRunner workflow automatically?
LearnWorlds doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LearnWorlds
$100 in credits. No card required. Connect in minutes.