Linking Clever 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 Clever connector syncs districts, schools, users, 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 the bearer token Clever issued to your app for a district. Find it in your Clever app dashboard, under that district's Data Sources tab in the API Token section. See the Clever API overview for details.
Each token is scoped to a single district - connect a separate source per district you want to sync. Rostering data beyond districts requires the district's Clever Secure Sync (Clever Complete) subscription.
You'll be asked for:
- District bearer token
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 Clever tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
District bearer token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Districts | A school district that has authorized your Clever application. | Full refresh | — | — |
Schools | A school within a district. | Full refresh | — | — |
Users | A student, teacher, staff member, district admin, or contact in the district roster. | Full refresh | — | — |
Sections | A class section: a group of students taught by a teacher for a course. | Full refresh | — | — |
Courses | A course offered by the district, made up of one or more sections. | Full refresh | — | — |
Terms | An academic term (semester, quarter, or school year) defined by the district. | Full refresh | — | — |
Contacts | A guardian or emergency contact, listed as a user with the | Full refresh | — | — |
Events | A created, updated, or deleted change event for a record in the district, from Clever's delta feed. Retained for 30 days. | Incremental, Full refresh | id | — |
Troubleshooting
- If the connection fails with an authorization error, the district bearer token 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.