--- title: "TalentLMS Integration" description: "Connect AI agents to your TalentLMS training portal. Agents create users, enroll them in onboarding courses, generate one-time auto-login URLs, track completion and progress, and organize learners across branches, groups, and categories." url: https://flowrunner.ai/integrations/talentlms date_modified: 2026-08-04T10:04:16-07:00 --- # TalentLMS [Education & LMS](https://flowrunner.ai/integrations/category/education-lms) Connect AI agents to your TalentLMS training portal. Agents create users, enroll them in onboarding courses, generate one-time auto-login URLs, track completion and progress, and organize learners across branches, groups, and categories. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 12 actions · Basic auth · available [TalentLMS website](https://talentlms.com/) · [Platform Documentation](https://www.talentlms.com/pages/docs/TalentLMS-API-Documentation.pdf) · Capability data verified 2026-08-12 1. A new hire is added to the HR system with a start date and department 2. Create User provisions their TalentLMS account with name, email, login, and timezone 3. Add User To Course enrolls them in the mandatory onboarding and compliance courses for their role 4. Get User Login URL generates a one-time sign-in link pointed at their first course 5. The welcome message delivers the auto-login link, so day one starts inside the training, not at a password reset 6. A weekly sweep runs Get Users In Course on the compliance courses and compares completion against each hire's deadline 7. The people ops manager reviews the overdue list and decides who gets a reminder, who gets a manager escalation, and whose deadline genuinely needs extending ## What This Integration Enables An LMS is only as good as the operations around it: who gets created, what they are enrolled in, whether they actually finish, and what happens when they do not. TalentLMS exposes all four to the API, and FlowRunner agents run them as a system. Provisioning flows from the HR record, enrollment flows from the role, completion flows into reporting, and the exceptions, the overdue, the unenrolled, the never-logged-in, flow to a person with enough context to act. - Create users from HR events with profile, timezone, and language set at signup - Enroll learners into courses as learner or instructor, idempotently: existing enrollments are returned, not duplicated - Generate one-time auto-login URLs that drop a learner directly into a course, unit, or page - Report per-course completion status, percentage, and dates for every enrolled learner - Track individual progress across all of a user's enrollments via their full profile - Organize automation across branches, groups, and categories on multi-team and multi-client portals ### Without FlowRunner **Provisioning waits for a login ticket**: New hires get LMS credentials in week two, and onboarding starts late by default **Completion tracking is a spreadsheet ritual**: Someone exports course reports monthly, and overdue compliance surfaces after the audit asks **Role changes outrun enrollments**: People keep courses from jobs they left and miss the ones their new role requires ### With FlowRunner **Training exists before the first morning**: The HR record creates the user, the enrollments, and the auto-login link in one pass **Compliance status is a monitored feed**: Weekly sweeps compare completion against deadlines and route exceptions to a person **Enrollments follow the org chart**: Role changes propose the course adds and removals, and a human approves the removals ## Use Case Scenarios ### Day-one onboarding that provisions itself A new employee appears in [BambooHR](https://flowrunner.ai/integrations/bamboohr). The agent calls Create User with their details, resolves the role's required courses from List Courses, and runs Add User To Course for each. Get User Login URL produces a one-time link targeting the first onboarding unit, delivered in the welcome email. When the hire clicks it, they are inside the course, no password, no ticket, no week-two catch-up. HR's system remains the single source of truth; the LMS mirrors it within minutes. ### Compliance reporting the auditor can have today Every Monday, the agent runs Get Users In Course against each mandatory compliance course and writes the roster to [Google Sheets](https://flowrunner.ai/integrations/google-sheets): learner, completion status, percentage, completion date. Learners past their deadline appear on an exceptions tab, and the summary posts to [Slack](https://flowrunner.ai/integrations/slack) for the people ops manager, who decides the escalation per person. When the auditor asks who completed data-handling training and when, the answer is a living sheet with a week's freshness, not a scramble. ### Multi-client training portals kept in sync by contract A company trains customer teams in separate TalentLMS branches. When a new client contact is added to the CRM, the agent checks List Branches for the client's sub-portal, creates the user, and enrolls them in the client's course bundle from List Groups. Quarterly, Get Course pulls per-client progress for the success team's business reviews. The training operation scales by client count without scaling the admin headcount, which is the point of a scale lever. ## Human-in-Loop Highlight Remove User From Course does not just unenroll: it removes the progress associated with the enrollment. For a compliance course, that progress record is evidence, the thing you show an auditor to prove a person completed their training and when. An automated role-change sync that removes courses too eagerly can delete the completion history the company is required to be able to produce. So FlowRunner splits enrollment changes by direction: Add User To Course flows freely, because TalentLMS makes it idempotent and the worst case is an extra course. Removals queue for review: "Role change for j.chen: proposing removal from 3 courses. One is Data Handling Certification, completed 2025-11-04. Remove anyway, or retain for the record?" The people ops manager keeps the completed compliance record and approves the other two. An enrollment can be recreated in a second. A completion record cannot. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 12 actions ### Users 4 - **List Users** Retrieves all users registered in the portal with id, name, email, login, user type, status, and enrollment counts. Returns the full list in a single response, so agents treat it as a bulk read on large portals. - **Get User** Retrieves a single user's full profile by id, including contact details, custom fields, and every course enrollment with completion status and progress. The per-learner progress view behind individual reporting. - **Create User** Creates a new user via the signup endpoint with first name, last name, email, login, and password, plus optional bio, timezone, and interface language. Returns the new user with their assigned id. The provisioning step behind onboarding automation. - **Get User Login URL** Generates a one-time sign-in URL that logs the user directly into TalentLMS, optionally redirecting to a specific course, unit, or page. Because the link grants account access, agents deliver it only to the learner's own verified address. ### Courses 2 - **List Courses** Retrieves all courses in the portal with id, name, code, category, description, price, status, and creation date, in a single non-paginated response. The catalog read behind role-to-course mapping. - **Get Course** Retrieves a single course by id with its units, enrolled users and their progress, category, and description. The per-course detail view behind client reviews and curriculum audits. ### Enrollment 3 - **Add User To Course** Enrolls an existing user into a course as learner or instructor. Already-enrolled users return their existing enrollment rather than a duplicate, which makes it safe inside automated syncs. - **Remove User From Course** Unenrolls a user from a course and removes the progress associated with the enrollment. The record-destroying operation this page's human gate exists for. - **Get Users In Course** Retrieves every user enrolled in a course with enrollment role, completion status, completion percentage, and completion date. The reporting step behind compliance sweeps. ### Structure 3 - **List Categories** Retrieves all course categories with id, name, price, and parent category id for nesting. Used to organize and filter courses in curriculum logic. - **List Groups** Retrieves all groups with id, name, description, group key, price, owner, and member count. The bundling mechanism behind bulk enrollment flows. - **List Branches** Retrieves all branches configured in the account with id, name, theme, timezone, language, and status. The map of isolated sub-portals behind multi-team and multi-client automation. ## Frequently Asked Questions ### What can FlowRunner do with TalentLMS? FlowRunner agents can run List Users, Get User, and Create User in TalentLMS, plus 9 more actions. ### Does connecting TalentLMS to FlowRunner require OAuth? No. TalentLMS connects to FlowRunner with basic authentication (a username and password), no OAuth flow required. ### Can TalentLMS trigger a FlowRunner workflow automatically? TalentLMS doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at TalentLMS?** This integration exposes TalentLMS to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/talentlms. Site index: https://flowrunner.ai/llms.txt