Linking Northpass LMS as a source
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.
Contents
This source is currently in alpha. The interface and available tables may change.
The Northpass LMS connector syncs people, courses, learning paths, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Northpass API key to sync your Northpass (Gainsight Customer Education) learning data.
You can create an API key in your Northpass admin panel under Apps → API Access.
You'll be asked for:
- API key
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Northpass LMS tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
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 |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.