Linking Kisi 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 Kisi connector syncs locks, places, users, groups, role assignments, controllers, and readers into the PostHog data warehouse, so you can analyze physical access control data alongside your product data.
Prerequisites
A Kisi API key with organization owner or administrator rights. 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.
Generate an API key in your Kisi account: go to My Account > API and click Add API Key. Your account must have organization owner or administrator rights.
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 Kisi tables use full refresh. Each sync replaces the contents of the table. This is because Kisi's API endpoints have no time filters for incremental syncing.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
locks | Doors controlled through Kisi, including their connection and lock status. | Full refresh | — | — |
places | Physical locations managed through Kisi. | Full refresh | — | — |
users | Users visible to the connected Kisi account. | Full refresh | — | — |
groups | Groups that define shared access rights in Kisi. | Full refresh | — | — |
role_assignments | Assignments that grant Kisi roles to users, teams, or guests. | Full refresh | — | — |
controllers | Kisi controllers and their connection status. | Full refresh | — | — |
readers | Kisi readers and their connection status. | 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 in My Account > API, then reconnect the source.
If a table syncs no rows, the credential may not have access to that data. Ensure your account has organization owner or administrator rights.
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.