Linking KnowBe4 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 KnowBe4 connector syncs your security awareness training and phishing simulation data into the PostHog Data warehouse, so you can analyze phishing risk scores, training completion rates, and campaign results alongside your product data.
Prerequisites
You need admin access to a KnowBe4 account to generate a Reporting API key. Keys are generated under Account Settings > API and are account-wide – there are no scopes to configure.
Your API key is only valid against the region where it was generated (US, EU, CA, UK, or DE), so make sure you select the matching region when connecting.
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.
When linking KnowBe4, you'll need:
- API key – generate a Reporting API key as an account admin under Account Settings > API. Keys are account-wide with no scopes to configure.
- Region – select the region matching the URL you sign in to. Options are US, EU, CA, UK, and DE. Your API key is only valid against the region it was generated in.
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 KnowBe4 tables sync as full refresh. The KnowBe4 API doesn't expose reliable server-side timestamp filters for incremental sync.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
users | Every user in the KnowBe4 account, one row per user, including their current phishing risk score. | Full refresh | — | — |
groups | Every group configured in the KnowBe4 account, one row per group. | Full refresh | — | — |
group_members | Membership rows linking each group to its member users. | Full refresh | — | — |
phishing_campaigns | Phishing campaigns configured in the account, including aggregate results across all of the campaign's security tests. | Full refresh | — | — |
phishing_security_tests | Individual phishing security tests (PSTs), including delivery and interaction result counts. | Full refresh | — | — |
phishing_security_test_recipients | Per-recipient results for a phishing security test, one row per user targeted by the test. | Full refresh | — | — |
training_campaigns | Training campaigns configured in the account, including assigned content and completion status. | Full refresh | — | — |
training_enrollments | Individual user enrollments in training campaign content (modules or uploaded policies). | Full refresh | — | — |
Troubleshooting
- If you get an authorization error, your API key is invalid or expired. Generate a new key under Account Settings > API and reconnect.
- If you get an authorization error after changing the region, your API key is only valid against the region where it was generated. Make sure the selected region matches your console URL.
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.