Two-way sync
Changes in Google Cloud Spanner or Kommo instantly reflect in both systems. No stale data, no manual imports.
Keep Google Cloud Spanner 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.
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 Google Cloud Spanner, where it can be queried and joined like everything else.
Stacksync mirrors Tasks, Notes, Custom Fields, Users from Kommo into Rows, Interleaved tables, Secondary indexes, Change streams in Google Cloud Spanner 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.
Signup, usage, or lifecycle changes written to Google Cloud Spanner sync onto the matching records in Kommo, giving go-to-market teams live product context.
Back-office apps read and write the synced tables; Stacksync handles the Kommo API, limits, and retries.
Field and stage updates in Kommo arrive as row changes in Google Cloud Spanner, ready to drive jobs and notifications.
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 Cloud Spanner objects | Kommo objects | |
|---|---|---|
| Change streams Capture inserts, updates, and deletes for log-style change data capture. | Notes Free-text and system notes attach context to synced leads and contacts. | |
| Views Read-only projections useful for shaping data before it leaves Spanner. | Custom Fields Per-entity custom fields hold data written from external databases and enrichment. | |
| Databases Top-level containers that scope schema and sync configuration. | Users Account users map lead ownership to people in other systems. | |
| Tables Relational tables mapped one-to-one to sync targets. | Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. | |
| Rows The unit of read and write in each sync cycle, keyed by primary key. | Leads The central pipeline record; external signups and form fills sync in as leads. | |
| Interleaved tables Child rows physically co-located with parents; synced as related records. | Contacts Person records sync with other CRMs and databases for a shared contact file. |
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Google Cloud Spanner–Kommo connection.
Changes in Google Cloud Spanner or Kommo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Google Cloud Spanner or Kommo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Google Cloud Spanner or Kommo record.
Track your Google Cloud Spanner ⇄ Kommo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Google Cloud Spanner and Kommo.
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.
Authenticate Google Cloud Spanner 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.
Pick the Google Cloud Spanner 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Google Cloud Spanner and Kommo: authenticate both systems, choose the objects to sync (such as Google Cloud Spanner's Change streams and Views), map fields visually, and changes propagate both ways in milliseconds — no code required.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Google Cloud Spanner and Kommo: Product events onto CRM records; Internal tools without API code; Trigger workflows from CRM changes. Signup, usage, or lifecycle changes written to Google Cloud Spanner sync onto the matching records in Kommo, giving go-to-market teams live product context.
Google Cloud Spanner: GRPC/REST client API with SQL query surface (GoogleSQL and PostgreSQL-interface dialects). Authentication: Google Cloud IAM (service accounts). Kommo: REST API. Authentication: OAuth 2.0 with refresh tokens. Stacksync manages authentication, retries, and rate limits on both sides.
Kommo: The API uses OAuth 2.0 with short-lived access tokens refreshed via refresh tokens, and supports webhooks on record lifecycle events. Google Cloud Spanner: Change streams record row-level inserts, updates, and deletes and can be consumed through the API for CDC pipelines. Stacksync's field mapping accounts for these differences between Google Cloud Spanner and Kommo without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Google Cloud Spanner and Kommo records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 386 integrations available for Google Cloud Spanner and Kommo.