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

Follow these steps to add Kommo as a source in Renta by authorizing access to your Kommo account.

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 pipeline

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

Create a Kommo pipeline

Link your Kommo source to a destination and configure the pipeline.

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.

Use the search field to find a parameter by name, or click Select All. The Selected tab shows everything you picked, and the Selected Parameters list below the picker lets you remove a parameter.

Each report type covers these parameters.

Report type	Parameters
Leads	ID, Name, Price, Responsible User ID, Group ID, Status ID, Pipeline ID, Loss Reason ID, Source ID, Created By, Updated By, Closed At, Created At, Updated At, Closest Task At, Is Deleted, Score, Account ID, Labor Cost, Is Price Modified by Robot, Custom fields values, Tags, Contacts, Companies
Contacts	ID, Name, First Name, Last Name, Responsible User ID, Group ID, Created By, Updated By, Created At, Updated At, Is Deleted, Closest Task At, Account ID, Custom fields values, Tags, Companies, Leads, Customers
Companies	ID, Name, Responsible User ID, Group ID, Created By, Updated By, Created At, Updated At, Closest Task At, Custom fields values, Tags, Contacts, Leads
Customers	ID, Name, Next Price, Next Date, Responsible User ID, Status ID, Periodicity, Created By, Updated By, Created At, Updated At, Closest Task At, Is Deleted, LTV, Purchases Count, Average Check, Account ID, Custom fields values, Tags, Contacts, Companies
Pipelines	ID, Name, Sort, Is Main, Is Unsorted On, Is Archive, Account ID, Statuses
Users	ID, Name, Email, Language, Leads Access Rights [Object], Contacts Access Rights [Object], Companies Access Rights [Object], Tasks Access Rights [Object], User Rights [Object]

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.