Linking Coassemble 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.
This source is currently in alpha. The interface and available tables may change.
The Coassemble connector syncs courses, collections, clients, 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 Coassemble workspace ID and API key to pull your courses, collections, learners, and learner progress.
You can generate an API key from your workspace API settings in Coassemble. API access must be enabled on your workspace plan.
You'll be asked for:
- Workspace ID
- 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 Coassemble tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Workspace ID | text | Yes |
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
courses | A course in the Coassemble workspace, including publish state and access settings. | Full refresh | — | — |
collections | A collection — an ordered group of courses shared and tracked together. | Full refresh | — | — |
clients | A client — a grouping of users in a headless workspace, typically one of your customers or tenants. | Full refresh | — | — |
users | A user (learner) identity in the headless workspace. | Full refresh | — | — |
course_trackings | A learner's progress record for a course (one row per learner per course attempt). | Full refresh | — | — |
screen_trackings | A learner's screen-level progress through a course (one row per learner per course), with each screen attempt and its per-question progress nested under | Full refresh | — | — |
collection_trackings | A learner's progress record for a collection (learning path), with the per-course breakdown nested under | Full refresh | — | — |
user_trackings | A learner's progress record for a course, keyed by learner rather than by course (one row per course the learner has taken). | Full refresh | — | — |
client_usage | Consumption for a client in the current billing period, one row per usage metric. | Full refresh | — | — |
client_allowances | The monthly allowance behind a client's usage, one row per usage metric — the denominator for client_usage. | Full refresh | — | — |
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.