Teachable

Connect AI agents to your Teachable school. Agents look up courses and users, grant or revoke enrollments as customers sign up or churn elsewhere, and report on per-student course progress and completion.

8 actions API key available

Teachable website ↗ Platform Documentation ↗ Capability data verified 2026-07-27

A purchase completes in the payment system for the flagship course bundle

List Users searches the school by the buyer's email to find or confirm their account

Enroll User grants access to each course in the bundle

The welcome sequence starts and the team channel logs the new enrollment

Get Course Progress runs weekly, reading each student's completion percentage and quiz results

Students stalled below the progress threshold for two weeks get a re-engagement email with a link to their next lecture

When a churn signal arrives, a failed payment or a cancellation, the owner decides whether access ends now, at period end, or not at all

Unenroll User executes the decision, and the CRM records what happened and why

What This Integration Enables

A course business is an access business: revenue events happen in the payment stack, learning happens in Teachable, and the enrollments connecting them are where manual work piles up. This connector hands that connective work to agents. FlowRunner agents look up courses and users, grant and revoke enrollments as customers sign up or churn elsewhere, and pull per-student progress and completion into the tools where follow-up actually happens. - Grant course access automatically on purchase, application approval, or cohort start - Revoke access on churn, deliberately, through review - Sync the course and student catalog into spreadsheets and CRMs - Audit who holds access to each course and how far they have progressed - Turn completion data into certificates, next-course offers, and win-back campaigns - Keep corporate cohorts, subscriptions, and one-time purchases all resolving to the same access truth Progress reporting is the quiet advantage here: Get User and Get Course Progress expose completion at the student and course level, which turns learning analytics from a dashboard you visit into a signal your workflows act on. The one action that touches a paying customer's access runs through FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate.

Without FlowRunner

Access managed by hand Every sale, refund, and cancellation means logging into the school admin to click enrollments

Progress data goes unread Completion percentages sit in Teachable while stalled students quietly become churned students

Revocations fire on raw signals A card hiccup can yank a good customer out of a course mid-lecture

With FlowRunner

Purchases become enrollments Payment events grant the right course access within a minute, at any hour

Progress drives the follow-up Stalls trigger re-engagement, completions trigger certificates and the next offer

Revocation is a decision Churn signals reach a person with the student's history, and access ends deliberately or not at all

Use Case Scenarios

The roster that enrolls itself

A corporate client sends a spreadsheet of forty learners for the certification course. The agent reads the roster from [Google Sheets](/integrations/google-sheets), resolves each person with List Users, and calls Enroll User for everyone confirmed in the school, reporting the handful of emails that need accounts created first. The client's program manager gets a completion-ready roster instead of a two-day data-entry job, [Slack](/integrations/slack) logs each enrollment as it lands, and the same workflow reruns cleanly when the client adds five more names next week.

The stalled-student rescue

Weekly, Get Course Progress reads every active course. Students who completed the first module then stopped get a personal-feeling nudge through [Gmail](/integrations/gmail) linking their next uncompleted lecture, pulled from the curriculum structure in Get Course. Students crossing 100 percent trigger the certificate email and the next-course recommendation while the accomplishment still feels fresh. The completion report appends to the analytics sheet, so the founder sees which lectures stall the most students and fixes the content, not just the symptoms.

Access reconciliation

Monthly, List Course Enrollments audits each paid course against the subscription ledger. Enrollments with no matching active subscription surface for review; subscribers missing their enrollments get fixed on the spot with Enroll User. Get User closes individual investigations with the student's full enrollment and completion history. Access and revenue stop drifting apart, in either direction, and the audit that used to consume a founder's Saturday becomes a report that arrives finished.

Human-in-Loop Highlight

Unenroll User revokes a real customer's access to content they paid for, and while the enrollment can be restored, the experience cannot: a student who opened lesson eight to find the course gone does not care that it was a webhook's mistake. The signals that trigger revocation are exactly the ambiguous kind, a failed renewal that is actually an expired card, a chargeback that is actually confusion. So the agent never revokes on signal alone. It assembles the case: "Payment failed for a.torres@ example, second retry pending. Enrolled in Certification Track, 82 percent complete, active four days ago. Revoke now, grant grace until the retry resolves, or hold?" The owner answers with the customer relationship in view, Unenroll User runs only on that answer, and the decision logs to the CRM. Enroll User passes through a lighter version of the same check on bulk runs, because granting forty seats against the wrong course is a refund conversation with a corporate client.

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

8 actions

Courses

List Courses Retrieves the school's courses with pagination and filters for name and published status, returning ID, name, heading, and published flag. The catalog step behind enrollment and reporting workflows.
Get Course Retrieves one course in full, including its lecture sections and lectures. The curriculum map used to point stalled students at their next step.

Users

List Users Retrieves the school's students, authors, and staff with pagination and filters by email and name. The resolution step before any enrollment change.
Get User Retrieves a user's full profile including their enrollments with per-course completion percentage and completion date. The one-call answer to "where is this student."

Enrollments

Enroll User Enrolls an existing user in a course, granting content access. The write that turns a purchase into a student.
Unenroll User Removes a user's enrollment, revoking content access. The reverse of Enroll User, and the action behind this page's human gate.
List Course Enrollments Retrieves all enrollments for a course with each user's enrollment date, completion percentage, and completion date. The audit step for access reconciliation.

Reports

Get Course Progress Retrieves per-student progress for a course: completion percentage, completed lectures, and quiz results where available. The signal that drives rescues, certificates, and content fixes.

Frequently Asked Questions

What can FlowRunner do with Teachable?

FlowRunner agents can run List Courses, Get Course, and List Users in Teachable, plus 5 more actions.

Does connecting Teachable to FlowRunner require OAuth?

No. Teachable connects to FlowRunner with an API key, no OAuth flow required.

Can Teachable trigger a FlowRunner workflow automatically?

Teachable doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Teachable

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us