Linking Kandji (Iru Endpoint Management) 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 Kandji (Iru Endpoint Management) connector syncs devices, blueprints, device details, 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.
Connect Kandji with a tenant-level API token, created in Kandji under Settings → Access. Your API URL is shown there too - enter its subdomain and pick the matching region (US or EU). The token needs read access to the devices, blueprints, and device-detail endpoints for the tables you want to sync.
You'll be asked for:
- API token
- Subdomain: for example
accuhive. - Region: choose between US (api.kandji.io) and EU (api.eu.kandji.io).
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 Kandji (Iru Endpoint Management) tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API token | password | Yes |
Subdomain | text | Yes |
Region | select | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
devices | Every device enrolled in your Kandji tenant, one row per device. | Full refresh | — | — |
blueprints | Configuration blueprints defined in your tenant that group library items and settings. | Full refresh | — | — |
device_details | Detailed inventory for each device (hardware, network, security, and OS sections). | Full refresh | — | — |
device_apps | Applications installed on each device, one row per device/app pairing. | Full refresh | — | — |
device_library_items | Library items (profiles, apps, scripts) applied to each device and their status. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API 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.