Skip to content
Database ⇄ CRM

Airtable to Kommo integration — real-time, two-way sync

Keep Airtable 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 Airtable and Kommo

Treat Kommo like part of your database: its records live in Airtable as real tables, and writes in either place sync to the other in seconds.

Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Airtable, where it can be queried and joined like everything else.

Stacksync mirrors Tasks, Notes, Custom Fields, Users from Kommo into Collaborators, Bases, Tables, Records in Airtable with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Kommo with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.

Common use cases

  • 01 Mirror pipeline stage changes into BI tools for forecasting
  • 02 Route leads that originate in WhatsApp or Instagram conversations into other systems of record
  • 03 Sync form-submitted records from Airtable into downstream systems like a helpdesk or marketing platform.
  • 04 Push CRM accounts and deals into an Airtable base so operations teams can manage pipelines and enrichment without CRM licenses.

Common sync patterns

Trigger workflows from CRM changes

Field and stage updates in Kommo arrive as row changes in Airtable, ready to drive jobs and notifications.

Query the CRM like a database

Accounts, contacts, and custom objects from Kommo become tables in Airtable you can join with application data directly.

Product events onto CRM records

Signup, usage, or lifecycle changes written to Airtable sync onto the matching records in Kommo, giving go-to-market teams live product context.

What you can sync between Airtable 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.

Airtable objects Kommo objects How this pairing syncs
Fields Typed columns including linked records, lookups, and rollups; computed fields are read-only in syncs. Contacts Person records sync with other CRMs and databases for a shared contact file. Fields is specific to Airtable and Contacts to Kommo — each maps to any object or custom field on the other side.
Views Filtered subsets of a table that can scope which records a sync reads. Companies Organization records map to accounts in ERPs and invoicing tools. Views is specific to Airtable and Companies to Kommo — each maps to any object or custom field on the other side.
Linked records Cross-table references that carry relationships between synced tables. Pipelines & Statuses Stage definitions structure lead progress and drive stage-change syncs to reporting tools. Linked records is specific to Airtable and Pipelines & Statuses to Kommo — each maps to any object or custom field on the other side.
Attachments File fields exposed as expiring URLs that syncs can mirror to other systems. Tasks Follow-up records keep rep activity consistent across systems. Attachments is specific to Airtable and Tasks to Kommo — each maps to any object or custom field on the other side.
Collaborators User fields useful for mapping record ownership to accounts in a CRM or database. Notes Free-text and system notes attach context to synced leads and contacts. Collaborators is specific to Airtable and Notes to Kommo — each maps to any object or custom field on the other side.
Bases Top-level containers; each base has its own API endpoint and schema. Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Bases is specific to Airtable and Custom Fields to Kommo — each maps to any object or custom field on the other side.

How changes propagate between Airtable and Kommo

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Airtable Kommo Sub-second propagation

DetectionAirtable pushes changes as they happen — webhook events backed by change data capture. Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks).

DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.

Kommo Airtable Sub-second propagation

DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.

DeliveryEach detected change is written to Airtable through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Airtable: The Web API enforces a per-base limit of 5 requests per second.
  • Kommo: Subject to per-account request rate limits.
What ships with Airtable ⇄ Kommo

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Airtable 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 Airtable or Kommo record.

Observability

Monitoring

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

Trading partners

EDI

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

How the Airtable and Kommo connectors work

Airtable

Integration surface
REST API (per-base Web API plus metadata and webhooks endpoints)
Authentication
OAuth (Airtable OAuth grant to specific bases or all resources); the authorizing user must have a `creator` role, since only creator roles can create webhooks
Change detection
Incremental updates: changes in Airtable are detected and synced efficiently in realtime (webhook-based — creator role required to create webhooks); formula fields don't emit change events and are re-synced every hour
Capabilities
read · write · CDC · webhooks
Rate limits
The Web API enforces a per-base limit of 5 requests per second.
Airtable setup guide

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 Airtable 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 Airtable 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
    Airtable connected
    Kommo connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Airtable 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 · Airtable ⇄ 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
    Airtable Kommo
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Airtable and Kommo integration FAQ

SECURITY

Security teams trust 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
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 553 integrations available for Airtable and Kommo.

Popular · 7 of 553
All Airtable 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