LearningSuite
Education & LMSConnect AI agents to LearningSuite, a German online course platform. Agents create and update members, assign courses and bundles, manage groups, and read, set, or reset course progress so member access always matches what customers bought.
What This Integration Enables
LearningSuite is a German course platform, and the first thing to understand about this connector is what it does not contain. There is no order, no invoice, no purchase and no payment object anywhere in its twenty-three actions. That is not an omission, it is the shape of the product: LearningSuite holds the learning, and the money lives in your checkout, your CRM, or your ERP. Every grant this connector makes is therefore the execution of a decision that was already taken somewhere else, which is exactly the situation where an agent is useful and exactly the situation where a wrong decision propagates silently.
The second thing worth understanding is that progress here is writable, not just readable. Most course platforms let an agent ask how far a learner got. LearningSuite lets an agent set it and reset it, either for the whole course or for named modules, lessons and pages. Get Member Course Progress reads the record, Set Member Course Progress marks content complete, and Reset Member Course Progress clears it. That combination turns the platform into something an agent can genuinely operate: a migration can carry prior completions across, a corrected curriculum can be re-opened for the cohort that took the old version, and a re-enrollment can start clean. It also means the learning record is a mutable object, which is the reason this page has the human-in-the-loop gate it has.
Around those two ideas sits the ordinary member surface, and it is complete. Members are found by email or id, created, updated, deactivated without deletion, and deleted permanently when that is genuinely what is wanted. Courses and bundles are assigned and removed individually, with a bundle grant unlocking every course inside it. Groups organize members into cohorts and take bulk membership changes in a single call, so cross-system cohort sync is one action rather than a loop. On the read side, List Course Members returns an enrollment roster with optional progress attached, and List Course Submissions surfaces assignment and quiz work waiting for a human to look at it. The API is rate limited to a hundred and twenty requests per minute, so large sweeps belong on a schedule rather than in a burst.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A buyer becomes a learner without anyone rekeying them
A purchase settles in Digistore24 or Stripe. The agent reads the order, maps the product to a LearningSuite bundle, and calls Find Member By Email to see whether this person already exists. New buyers get Create Member followed by Assign Bundles To Member; returning buyers get the bundle added to the account they already have, so a second purchase does not create a second identity. Add Members To Groups drops them into the cohort for their intake month. A welcome message goes out through Gmail with their login details. Orders whose product has no mapped bundle do not guess at a match, they are held as automation exceptions with the product name attached, because a wrong bundle grants content nobody paid for.
Inactivity that reaches a coach instead of a dashboard
List Members accepts an inactivity filter, meaning members who have not logged in for at least a given number of days, and it can optionally include the ones who never logged in at all. That second group is the interesting one, because a learner who never started is a refund conversation and a learner who stalled at module four is a coaching conversation. The agent runs the sweep on a schedule, uses Get Member Courses and Get Member Course Progress to work out which of the two each person is, and posts the split list to the coaching channel in Slack with the course and the last known position named for each learner. The coach picks up a queue of people, not a percentage.
A cohort migrating to a rebuilt course
The curriculum team rebuilds a course and the old version is retired. The agent calls List Course Members on the old course to get the roster, Get Member Course Progress for each learner to capture where they actually were, then Assign Courses To Member for the new version and Set Member Course Progress to mark the modules whose content did not change. Remove Courses From Member retires the old enrollment once the new one is confirmed. This is the scenario that makes the writable progress surface worth having, and it is also the one that never runs unattended: a person signs off the module mapping before a single record is written, because the mapping is a judgment about equivalence, not a lookup.
Human-in-Loop Highlight
The gate on this connector sits on the learning record itself. Set Member Course Progress and Reset Member Course Progress are the two actions that change what a learner is recorded as having done, and both accept a Whole Course flag that applies to everything at once. A reset with that flag clears a learner's history, and there is no undo action on this connector to put it back. A set with that flag marks somebody complete who may not have opened a lesson. Certificates, continuing education claims, employer reimbursement and refund arguments all rest on that record, so an agent that quietly corrects it is not tidying data, it is rewriting evidence.
So the agent does the part that is mechanical and stops before the part that is a judgment. It sweeps the school, resolves every course instance id through Get Member Courses, reads every progress record, and assembles the discrepancies with the evidence attached. Then it asks in Slack: "Fourteen learners on Onboarding Basics show all modules complete but the course itself is not marked finished. Issue their certificates, correct the course record with Set Member Course Progress, or leave the records as they are?" That is the digital andon cord applied to a learning record. The agent found the anomaly, gathered the context, and pulled the line rather than choosing an answer that only looks harmless because it is small.
One reversible and one permanent action deserve naming for the same reason. Set Member Activation blocks a lapsed member from logging in while keeping their data and enrollments intact, and it can be turned straight back on, so a dunning flow can take it without asking. Delete Member removes the member and their access to every course and bundle permanently. Those two are not interchangeable, and a flow that reaches for the second when a subscription lapses has confused an unpaid invoice with a departure.
Agent Capabilities
23 actionsMembers
7- Find Member By Email Looks up a single member by email address and returns their profile, optionally with their group memberships. The lookup that decides whether a buyer becomes a new record or an addition to an existing one. Returns a not found error rather than an empty result when the email is unknown.
- Get Member Retrieves a member by their unique member id, with contact details, account status, and optionally their groups. Used once an id is already in hand from an earlier step.
- List Members Pages through the members of the account, with an inactivity filter for people who have not logged in for a given number of days and an option to include those who never logged in. The read behind every re-engagement and lapsed-access sweep.
- Create Member Creates a member from an email, first name and last name. The email must be unique, so this is the write that follows a failed lookup, not a blind attempt.
- Update Member Changes a member's first or last name. Only the fields supplied are touched, so a name correction from a CRM does not disturb the rest of the record.
- Delete Member Permanently removes a member and their access to every course and bundle. This cannot be undone, which is why lapsed subscriptions belong on Set Member Activation instead.
- Set Member Activation Activates or deactivates a member's login while keeping their data and enrollments. The reversible lever, and the right one for a payment that failed rather than a relationship that ended.
Course Progress
6- Assign Courses To Member Grants access to one or more courses by id, leaving existing enrollments in place. The core fulfillment action for a single-course purchase.
- Remove Courses From Member Revokes access to named courses without deleting the member. Used for refunds, downgrades, and retiring an old course version after a migration.
- Get Member Courses Lists everything a member is enrolled in, including the course instance id that every progress operation needs. Always the step before reading or writing progress, because the instance id is not the catalog course id.
- Get Member Course Progress Returns a member's completed modules and lessons and their overall completion for one course instance. The read behind certificates, coaching triage, and completion reporting.
- Set Member Course Progress Marks content complete for a member, either the whole course or named modules, lessons and pages. This writes the record a certificate is issued against, so it belongs behind a person in anything that touches live learners.
- Reset Member Course Progress Clears a member's progress, either wholesale or for named content. There is no undo on this connector, so a reset is the end of that learner's recorded history for the content it covers.
Bundles
2- Assign Bundles To Member Grants access to one or more bundles, unlocking every course each bundle contains. The single action behind most multi-course purchases.
- Get Member Bundles Lists the bundles a member currently holds, with each bundle's id and name. The entitlement check before an upsell or a renewal.
Courses
4- List Published Courses Returns the published courses in the account with their ids and titles. The catalog read that maps a product name on an order to something this connector can grant.
- Get Course Modules Retrieves a course's module structure with ids and titles. Used to build a progress write that targets specific modules rather than the whole course.
- List Course Members Pages through the members enrolled in one course, optionally with each person's progress attached. The roster read behind cohort reporting and course migrations.
- List Course Submissions Pages through learner submissions for a course, such as assignment or quiz work. The queue that routes real learner output to a human reviewer.
Groups
4- List Groups Returns the member groups in the account with their ids and names. Groups are how cohorts and bulk access are organized here.
- Create Group Creates a group with a given name and returns its id. Used to spin up an intake cohort or a client-specific group on demand.
- Add Members To Groups Adds many members to many groups in one call, with every listed member added to every listed group. The action that makes cohort sync from an external system a single step.
- Remove Members From Groups Removes many members from many groups in one call. The counterpart used when a cohort closes or an external system drops someone from a segment.
Frequently Asked Questions
What can FlowRunner do with LearningSuite?
FlowRunner agents can run Find Member By Email, Get Member, and List Members in LearningSuite, plus 20 more actions.
Does connecting LearningSuite to FlowRunner require OAuth?
No. LearningSuite connects to FlowRunner with an API key, no OAuth flow required.
Can LearningSuite trigger a FlowRunner workflow automatically?
LearningSuite doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with LearningSuite
$100 in credits. No card required. Connect in minutes.