Which Kommo account does the connection use?

The one you pick on the Kommo consent screen during authorization. The connection is tied to that account's subdomain, and the subdomain is shown on the connection card when you build a pipeline.

Why is there no date range in the pipeline settings?

Kommo reports are snapshots of the current CRM records, not date-based statistics. Renta downloads the full list of records on every run, so there is no historical window to configure.

What happens to records deleted in Kommo?

The destination table is replaced on every run, so it mirrors what the Kommo API returns at that moment. The Leads , Contacts , and Customers reports also offer an Is Deleted parameter you can select.

Why does the Customers report load zero rows?

The customers feature must be enabled in your Kommo account. When it is off, the Kommo API returns no data for this object and the run completes with an empty table.

Kommo

Kommo is a CRM that lives on your account subdomain, such as yourcompany.kommo.com. Its API exposes the core CRM objects: leads, contacts, companies, recurring customers, lead pipelines with their stages, and account users.

Renta exports each object to your data warehouse as a separate report type. A run downloads the current state of the records, including custom fields, tags, and the IDs of linked entities.

Authentication

Renta connects to Kommo through OAuth. You log in, choose which Kommo account to connect, and allow access. You do not need to copy any API keys from the Kommo settings.

Connect Kommo source

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the CRM category and click the Kommo card.

Kommo card in the CRM category of the Renta catalog

Start the authorizationStep 2

Click Log in to your Kommo account. Renta redirects you to the Kommo consent page.

Add a new Kommo connection page with the Log in to your Kommo account button

Grant access in KommoStep 3

If you manage several Kommo accounts, pick the one to connect in the account dropdown.
Click Allow.

You can revoke the granted permissions at any time in your Kommo profile or in the integration settings on the Kommo side.

Kommo consent screen with the account selector and the Allow button

Name the connection and saveStep 4

In the Source name field, specify a name for this data source. It is used exclusively in the Renta interface.
Click Save.

The Access granted card shows the connected account. The Re-authorize button next to it repeats the OAuth flow if you later need to switch the account.

Kommo connection setup with the source name field and the Save button

Source createdStep 5

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Kommo source in the Active status

Create a Kommo pipeline

Once the source is connected, create a pipeline to sync your Kommo data into your destination.

Select Kommo as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Kommo under Already connected and click Next step.

Select a source step with Kommo under Already connected

Select your Kommo connectionStep 2

Choose the Kommo connection you created earlier and click Next step. The card shows the subdomain of the connected account.

Select your Kommo connection step with the account subdomain shown on the connection card

Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected

Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

Pipeline configuration

On the final step, choose the report, pick its fields, and set the schedule.

Report type

Select which Kommo object the pipeline exports. One pipeline loads one report type.

Report type	Description
Leads	Deal records: budget, status and pipeline IDs, creation, update, and close dates, custom fields, tags, and the IDs of linked contacts and companies.
Contacts	Contact records: names, custom fields, tags, and the IDs of linked leads, companies, and customers.
Companies	Company records: attributes, custom fields, tags, and the IDs of linked contacts and leads.
Customers	Recurring customer records: next purchase date and amount, LTV, purchase count, and average check.
Pipelines	The account's lead pipelines together with their stages: stage IDs, names, and order.
Users	Account users: name, email, language, and access rights to leads, contacts, companies, and tasks.

Parameters

Select the Kommo fields to include in the destination table.

Report type

Name	API name	Description
ID int	`id`	ID of the company.
Name text	`name`	Name of the company.
Responsible User ID int	`responsible_user_id`	ID of the user responsible for the company.
Group ID int	`group_id`	ID of the group to which the responsible user belongs.
Created By int	`created_by`	ID of the user who created the company.
Updated By int	`updated_by`	ID of the user who last updated the company.
Created At int	`created_at`	Date of creation of the company, passed in Unix Timestamp.
Updated At int	`updated_at`	Date of update of the company, passed in Unix Timestamp.
Closest Task At int	`closest_task_at`	Date of the nearest task to be performed, passed in Unix Timestamp.
Custom fields values structure	`custom_fields_values`	Array of custom fields with additional information.
Tags structure	`tags`	Array of tags with additional information.
Contacts structure	`contacts`	Array of contact with additional information.
Leads structure	`leads`	Array of company additional information.

Name	API name	Description
ID int	`id`	ID of the contact.
Name text	`name`	Name of the contact.
First Name text	`first_name`	First name of the contact.
Last Name text	`last_name`	Last name of the contact.
Responsible User ID int	`responsible_user_id`	ID of the user responsible for the contact.
Group ID int	`group_id`	ID of the group to which the responsible user belongs.
Created By int	`created_by`	ID of the user who created the contact.
Updated By int	`updated_by`	ID of the user who last updated the contact.
Created At int	`created_at`	Date of creation of the contact, passed in Unix Timestamp.
Updated At int	`updated_at`	Date of update of the contact, passed in Unix Timestamp.
Is Deleted bool	`is_deleted`	Whether the contact is deleted or not.
Closest Task At int	`closest_task_at`	Date of the nearest task to be performed, passed in Unix Timestamp.
Account ID int	`account_id`	ID of the account in which the contact is located.
Custom fields values structure	`custom_fields_values`	Array of custom fields with additional information.
Tags structure	`tags`	Array of tags with additional information.
Companies structure	`companies`	Array of contact with additional information.
Leads structure	`leads`	Array of company additional information.
Customers structure	`customers`	Array of customers additional information.

Name	API name	Description
ID int	`id`	ID of the lead.
Name text	`name`	Name of the lead.
Price int	`price`	Budget of the lead.
Responsible User ID int	`responsible_user_id`	ID of the user responsible for the lead.
Group ID int	`group_id`	ID of the group which the responsible user belongs to.
Status ID int	`status_id`	ID of the status the lead is added to, by default – the first stage of the main pipeline.
Pipeline ID int	`pipeline_id`	ID of the pipeline the lead is added to.
Loss Reason ID int	`loss_reason_id`	ID of the reason for lead rejection.
Source ID int	`source_id`	Required GET parameter with. ID of the lead source.
Created By int	`created_by`	ID of the user who created the lead.
Updated By int	`updated_by`	ID of the user who last updated the lead.
Closed At int	`closed_at`	Closure date of the lead, passed in Unix Timestamp.
Created At int	`created_at`	Creation date of the lead, passed in Unix Timestamp.
Updated At int	`updated_at`	Update date of the lead, passed in Unix Timestamp.
Closest Task At int	`closest_task_at`	Date of the nearest task to be performed, passed in Unix Timestamp.
Is Deleted bool	`is_deleted`	Whether the lead is deleted or not.
Score int	`score`	Scoring of the lead.
Account ID int	`account_id`	ID of the account in which the lead is located.
Labor Cost int	`labor_cost`	Labor cost field type shows how much time was spent working on the lead. Time measured in seconds.
Is Price Modified by Robot bool	`is_price_modified_by_robot`	Required GET parameter with. Whether the lead's budget was last modified by a robot.
Custom fields values structure	`custom_fields_values`	Array of custom fields with additional information.
Tags structure	`tags`	Array of tags with additional information.
Contacts structure	`contacts`	Array of contact with additional information.
Companies structure	`companies`	Array of company additional information.

Name	API name	Description
ID int	`id`	ID of the pipeline.
Name text	`name`	Name of the pipeline.
Sort int	`sort`	Sort order of the pipeline.
Is Main bool	`is_main`	Whether the pipeline is the main one.
Is Unsorted On bool	`is_unsorted_on`	Whether the unsorted feature is enabled in the pipeline.
Is Archive bool	`is_archive`	Whether the pipeline is archived.
Account ID int	`account_id`	ID of the account in which the pipeline is located.
Statuses structure	`statuses`	Array of custom statuses fields with additional information.

Name	API name	Description
ID int	`id`	ID of the customer.
Name text	`name`	Name of the customer.
Next Price int	`next_price`	Expected purchase amount.
Next Date int	`next_date`	Expected date of the next purchase. Data in Unix Timestamp.
Responsible User ID int	`responsible_user_id`	ID of the user responsible for the customer.
Status ID int	`status_id`	ID of the customer's status in the account.
Periodicity int	`periodicity`	Periodicity (data required for customers with enabled periodicity functionality).
Created By int	`created_by`	ID of the user who created the customer.
Updated By int	`updated_by`	ID of the user who last updated the customer.
Created At int	`created_at`	Date of creation of the customer, passed in Unix Timestamp.
Updated At int	`updated_at`	Date of update of the customer, passed in Unix Timestamp.
Closest Task At int	`closest_task_at`	Date of the nearest task to be performed, passed in Unix Timestamp.
Is Deleted bool	`is_deleted`	Whether the customer is deleted or not.
LTV int	`ltv`	Total purchase amount.
Purchases Count int	`purchases_count`	Number of purchases.
Average Check int	`average_check`	Average purchase size.
Account ID int	`account_id`	ID of the account in which the customer is located.
Custom fields values structure	`custom_fields_values`	Array of custom fields with additional information.
Tags structure	`tags`	Array of tags with additional information.
Contacts structure	`contacts`	Array of contact with additional information.
Companies structure	`companies`	Array of company additional information.

Name	API name	Description
ID int	`id`	ID of the user.
Name text	`name`	Full name of the user.
Email text	`email`	Email address of the user.
Language text	`lang`	Language of the user. One of the options: ru, en, es.
Leads Access Rights [Object] structure	`leads`	Object containing user's access rights to leads.
Contacts Access Rights [Object] structure	`contacts`	Object containing user's access rights to contacts.
Companies Access Rights [Object] structure	`companies`	Object containing user's access rights to companies.
Tasks Access Rights [Object] structure	`tasks`	Object containing user's access rights to tasks.
User Rights [Object] structure	`rights`	Object containing user's system-wide rights and permissions.

Pick the fields one by one, or check the entire list with Select All.

Structured parameters load as nested records. Custom fields values keeps one record per custom field with its ID, name, code, type, and value. Tags, Statuses, the lists of linked entities (Contacts, Companies, Leads, Customers), and the access-rights objects of the Users report work the same way.

Date parameters such as Created At, Updated At, Closed At, and Next Date arrive as Unix timestamps.

If a custom field holds several values, the field_value column keeps the first one.

Table name

Name the pipeline and the destination table.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
Table name.
The destination table name. You can keep the auto-generated name or enter your own.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new Kommo integration in the Completed status

Sync strategy

All Kommo report types synchronize the same way.

Strategy	Supported report types	Description
Full reload	Leads, Contacts, Companies, Customers, Pipelines, Users	Kommo objects are snapshots of the current CRM state without a date column to partition by. On every run Renta downloads the complete list of records and replaces the contents of the destination table, so the table always mirrors the CRM at the time of the run.

Because every run reloads the whole object, the pipeline has no date range or overwrite period settings.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.