
Northpass LMS
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Connect Northpass LMS to PostHog to sync your data into the PostHog data warehouse for analysis and modeling.
Enter your Northpass API key to sync your Northpass (Gainsight Customer Education) learning data into the PostHog Data warehouse.
You can create an API key in your Northpass admin panel under Apps → API Access.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Linking Northpass LMS to PostHog
- Go to the Data pipeline page in PostHog
- Click New source and select Northpass LMS
- Fill in the required configuration fields
- Click Next, select the tables you want to sync, and then press Import
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
people | Learners and admins in your Northpass school. One row per person. | Full refresh | — | id |
courses | Courses available in your Northpass school. One row per course. | Full refresh | — | id |
learning_paths | Learning paths (ordered collections of courses). One row per learning path. | Full refresh | — | id |
categories | Categories used to organize courses. One row per category. | Full refresh | — | id |
groups | Groups that people can belong to. One row per group. | Full refresh | — | id |
quizzes | Quizzes configured across your courses. One row per quiz. | Full refresh | — | id |
course_enrollments | Enrollments for every course. Fans out one request per course. Full refresh only. | Full refresh | — | course_id, id |
learning_path_enrollments | Enrollments for every learning path. Fans out one request per learning path. Full refresh only. | Full refresh | — | learning_path_id, id |
course_activities | Activities (lessons) that make up every course. Fans out one request per course. Full refresh only. | Full refresh | — | course_id, id |
activity_events | Lesson-level learning events (e.g. learner viewed an activity), one row per person, activity, and timestamp. Re-syncs the full history on every run, so it is off by default. | Full refresh | — | person_id, activity_id, type, created_at |
quiz_attempts | Completed quiz attempts with score and passing threshold, one row per attempt. Built from quiz-completed events in the sent-webhooks log, which requires a webhook subscribed to those events and keeps three months of history, so the table is off by default. Full refresh only. | Full refresh | — | id |
quiz_attempt_answers | Per-question learner answers for every completed quiz attempt. Fans out one request per attempt found in the sent-webhooks log (same coverage caveats as quiz_attempts), so the table is off by default. Full refresh only. | Full refresh | — | quiz_attempt_id, id |