Linking Kommo 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 Kommo connector syncs leads, contacts, companies, 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.
In Kommo, go to Settings > Integrations and create a private integration, then open Keys and scopes and generate a long-lived token. The token inherits the rights of the user who created it, so create it as an admin if you want to sync users and account-wide lists.
You'll be asked for:
- Account subdomain: for example
mycompany. - Long-lived access 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 Kommo tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
Account subdomain | text | Yes |
Long-lived access token | password | Yes |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
Leads | A sales opportunity moving through a Kommo pipeline, with its stage, price, and owner. | Incremental, Full refresh | updated_at | — |
Contacts | A person in the Kommo account, linked to the leads and companies they belong to. | Incremental, Full refresh | updated_at | — |
Companies | An organization in the Kommo account, linked to its contacts and leads. | Incremental, Full refresh | updated_at | — |
LeadNotes | Notes and logged interactions attached to leads, including calls and system messages. | Incremental, Full refresh | updated_at | — |
ContactNotes | Notes and logged interactions attached to contacts. | Incremental, Full refresh | updated_at | — |
CompanyNotes | Notes and logged interactions attached to companies. | Incremental, Full refresh | updated_at | — |
Tasks | A to-do assigned to a user against a lead, contact, or company. | Full refresh | — | — |
Events | The account's change feed: stage moves, field edits, and other recorded actions. | Full refresh | — | — |
Pipelines | A lead pipeline, with its stages returned under | Full refresh | — | — |
Users | A user of the Kommo account, with their access rights. Requires an admin token. | Full refresh | — | — |
Catalogs | A Kommo list (catalog), such as a product or supplier list. | Full refresh | — | — |
LeadCustomFields | Custom field definitions available on leads. | Full refresh | — | — |
ContactCustomFields | Custom field definitions available on contacts. | Full refresh | — | — |
CompanyCustomFields | Custom field definitions available on companies. | Full refresh | — | — |
LeadTags | Tags that can be applied to leads. | Full refresh | — | — |
ContactTags | Tags that can be applied to contacts. | Full refresh | — | — |
CompanyTags | Tags that can be applied to companies. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the long-lived access 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.