Kommo (formerly amoCRM) is a messaging-powered CRM platform that helps businesses manage leads, contacts, and sales pipelines through a conversation-driven approach. It centralizes communication channels and provides tools for sales automation, pipeline management, and team collaboration.

Configuring Kommo as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Kommo option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

You’ll need a long-lived API token from your Kommo account. To generate one, go to Settings > Integrations in your Kommo account and create an integration to obtain the token. The following configurations are available:

API Key: The long-lived API token for authenticating with your Kommo account.
Subdomain: Your Kommo account subdomain. For example, if your Kommo URL is mycompany.kommo.com, your subdomain is mycompany.
Start Date: (Optional) The earliest date from which records will be synced for incremental streams.

Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.

Tip: The stream can be found more easily by typing its name.

Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
Sync Type: you can choose between INCREMENTAL and FULL_TABLE.
- Incremental: every time the extraction happens, we’ll get only the new data - which is good if, for example, you want to keep every record ever fetched.
- Full table: every time the extraction happens, we’ll get the current state of the data - which is good if, for example, you don’t want to have deleted data in your catalog.

Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:

Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Kommo and their corresponding fields:

Leads

Sales leads (deals) in your Kommo CRM. Supports incremental sync via updated_at.

Field	Type	Description
id	integer	Lead identifier
name	string	Lead name
price	integer	Sale amount
responsible_user_id	integer	Assigned user ID
group_id	integer	Group identifier
status_id	integer	Current pipeline stage ID
pipeline_id	integer	Pipeline identifier
loss_reason_id	integer	Reason for lead loss
created_by	integer	Creator user ID
updated_by	integer	Last editor user ID
created_at	integer	Creation timestamp (Unix)
updated_at	integer	Last update timestamp (Unix)
closed_at	integer	Closure timestamp (Unix)
closest_task_at	integer	Next task completion date (Unix)
is_deleted	boolean	Whether the lead is deleted
custom_fields_values	string	Custom field values (JSON)
score	integer	Lead score
account_id	integer	Account identifier
labor_cost	integer	Associated labor costs
is_price_computed	boolean	Whether price was computed
source_id	integer	Lead source identifier
is_price_modified_by_robot	boolean	Whether price was set by automation
tags	string	Associated tags (JSON)

Contacts

Contacts (people) in your Kommo CRM. Supports incremental sync via updated_at.

Field	Type	Description
id	integer	Contact identifier
name	string	Contact full name
first_name	string	First name
last_name	string	Last name
responsible_user_id	integer	Assigned user ID
group_id	integer	Group identifier
created_by	integer	Creator user ID
updated_by	integer	Last editor user ID
created_at	integer	Creation timestamp (Unix)
updated_at	integer	Last update timestamp (Unix)
closest_task_at	integer	Next task completion date (Unix)
is_deleted	boolean	Whether the contact is deleted
is_unsorted	boolean	Whether the contact is unsorted
custom_fields_values	string	Custom field values (JSON)
account_id	integer	Account identifier
tags	string	Associated tags (JSON)

Companies

Companies (organizations) in your Kommo CRM. Supports incremental sync via updated_at.

Field	Type	Description
id	integer	Company identifier
name	string	Company name
responsible_user_id	integer	Assigned user ID
group_id	integer	Group identifier
created_by	integer	Creator user ID
updated_by	integer	Last editor user ID
created_at	integer	Creation timestamp (Unix)
updated_at	integer	Last update timestamp (Unix)
closest_task_at	integer	Next task completion date (Unix)
is_deleted	boolean	Whether the company is deleted
custom_fields_values	string	Custom field values (JSON)
account_id	integer	Account identifier
tags	string	Associated tags (JSON)

Pipelines

Sales pipelines configuration. Full table sync.

Field	Type	Description
id	integer	Pipeline identifier
name	string	Pipeline name
sort	integer	Sort order
is_main	boolean	Whether this is the main pipeline
is_unsorted_on	boolean	Whether unsorted leads are enabled
is_archive	boolean	Whether the pipeline is archived
account_id	integer	Account identifier

Pipeline Statuses

Pipeline stages/statuses. Full table sync. Each status belongs to a pipeline.

Field	Type	Description
id	integer	Status identifier
name	string	Status name
sort	integer	Sort order within pipeline
is_editable	boolean	Whether the status can be edited
pipeline_id	integer	Parent pipeline identifier
color	string	Status color code
type	integer	Status type
account_id	integer	Account identifier
conditions	string	Stage conditions (JSON)

Tasks

Tasks linked to leads, contacts, or companies. Supports incremental sync via updated_at.

Field	Type	Description
id	integer	Task identifier
created_by	integer	Creator user ID
updated_by	integer	Last editor user ID
created_at	integer	Creation timestamp (Unix)
updated_at	integer	Last update timestamp (Unix)
responsible_user_id	integer	Assigned user ID
group_id	integer	Group identifier
entity_id	integer	Linked entity ID
entity_type	string	Linked entity type (lead, contact, company)
duration	integer	Task duration
is_completed	boolean	Whether the task is completed
task_type_id	integer	Task type identifier
text	string	Task description
result	string	Task result
complete_till	integer	Task deadline (Unix)
account_id	integer	Account identifier

Events

Activity events and audit trail. Supports incremental sync via created_at.

Field	Type	Description
id	string	Event identifier
type	string	Event type
entity_id	integer	Related entity ID
entity_type	string	Related entity type
created_by	integer	User who triggered the event
created_at	integer	Event timestamp (Unix)
value_after	string	Value after the change (JSON)
value_before	string	Value before the change (JSON)
account_id	integer	Account identifier

Users

Team members and users. Full table sync.

Field	Type	Description
id	integer	User identifier
name	string	User full name
email	string	User email address
lang	string	User language
rights	string	User permissions (JSON)

Data Model

The following diagram illustrates the relationships between the Kommo streams:

Documentation

Get started

Using Nekt

Workspace

Resources

Kommo as a data source

Configuring Kommo as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Documentation

Get started

Using Nekt

Workspace

Resources

Documentation Index

​Configuring Kommo as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Data Model

Configuring Kommo as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model