Skip to content
Business productivity ⇄ CRM

Google Sheets to Kommo integration — real-time, two-way sync

Keep Google Sheets and Kommo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from Mulesoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Google Sheets and Kommo

Sync what happens in Google Sheets with the customer records in Kommo, in real time and in both directions.

The CRM is supposed to be the record of every customer relationship, but customer-relevant information also accumulates in the other tools a team runs. Whatever Google Sheets holds or produces that touches a customer, whether conversations, payments, replies, enriched data, or notes, the CRM only benefits if it arrives without someone copying it over.

Stacksync connects Sheets (tabs), Rows, Ranges, Named ranges in Google Sheets to Chats, Leads, Contacts, Companies in Kommo with bi-directional, real-time sync. Activity and record changes in Google Sheets update the matching contact or account in Kommo, and CRM data flows the other way wherever Google Sheets can store and use it.

Common use cases

  • Publish pipeline, revenue, or inventory snapshots from a warehouse into a shared sheet for reporting.
  • Use a sheet as a lightweight intake form whose rows become records in a production database.
  • Replicate Kommo leads and contacts into a database or warehouse for reporting beyond built-in dashboards
  • Push web form and product signups into Kommo pipelines as they are submitted so messenger-based follow-up starts quickly

Where Google Sheets can store CRM context: fields kept current

Owner, lifecycle stage, or account details from Kommo sync into Google Sheets, so people working there have the context without switching tools.

Where Google Sheets supplies contact or company data

Enriched fields land directly on records in Kommo, and refreshes keep them from going stale.

Where Google Sheets processes payments

Charges, refunds, and subscription changes appear on the account in Kommo, so revenue context lives with the relationship.

What you can sync between Google Sheets and Kommo

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Google Sheets objects Kommo objects
Sheets (tabs) Individual worksheets, typically mapped one-to-one to a synced table. Custom Fields Per-entity custom fields hold data written from external databases and enrichment.
Rows Treated as records; a header row usually defines field names. Users Account users map lead ownership to people in other systems.
Ranges Addressed in A1 notation for batched reads and writes. Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts.
Named ranges Stable references that keep sync mappings valid when the grid moves. Leads The central pipeline record; external signups and form fills sync in as leads.
Cell values Untyped by default, so syncs handle type coercion for dates and numbers. Contacts Person records sync with other CRMs and databases for a shared contact file.
Spreadsheets The file-level container a sync connects to, identified by spreadsheet ID. Companies Organization records map to accounts in ERPs and invoicing tools.
What ships with Google Sheets ⇄ Kommo

Connect Google Sheets and Kommo for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Sheets–Kommo connection.

Real-time

Two-way sync

Changes in Google Sheets or Kommo instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Google Sheets or Kommo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Google Sheets or Kommo record.

Observability

Monitoring

Track your Google Sheets ⇄ Kommo sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Google Sheets and Kommo.

How the Google Sheets and Kommo connectors work

Google Sheets

Integration surface
REST API (Google Sheets API), with file-level change signals available through the Drive API
Authentication
OAuth 2.0 (user consent) or Google service accounts
Change detection
Polling; the Sheets API has no cell-level webhooks, and Drive push notifications only signal file-level changes
Capabilities
read · write
Rate limits
Subject to per-minute read and write quotas per project and per user, so large syncs are batched.

Kommo

Integration surface
REST API
Authentication
OAuth 2.0 with refresh tokens
Change detection
Webhooks on record add and update events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-account request rate limits
How it works

How to connect Google Sheets to Kommo — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Google Sheets and Kommo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Google Sheets connected
    Kommo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Google Sheets and Kommo objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Google Sheets ⇄ Kommo
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Google Sheets Kommo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Google Sheets and Kommo integration FAQ

SECURITY

Security teams love Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Google Sheets and Kommo.

Popular · 8 of 386
All Google Sheets integrations All Kommo integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own