Two-way sync
Changes in Smartsheet or TiDB instantly reflect in both systems. No stale data, no manual imports.
Keep Smartsheet and TiDB in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Engineers integrate with tools like Smartsheet through APIs, which means auth, pagination, rate limits, webhooks, and retry logic, all maintained forever and all different for every tool. Meanwhile the data would be trivial to use if it simply lived in TiDB.
Stacksync mirrors Attachments, Discussions and Comments, Users and Groups, Sheets from Smartsheet into Databases, Tables, Views, Columns in TiDB and keeps both sides in sync in real time. Your services query the database directly, and inserts or updates your code makes flow back into Smartsheet, so the tool and the database never disagree.
Write to the synced tables in TiDB and Stacksync propagates the change into Smartsheet, replacing custom integration code.
Updates in Smartsheet arrive as row changes in TiDB, so triggers, jobs, and services can respond in near real time.
Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.
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.
| Smartsheet objects | TiDB objects | How this pairing syncs | |
|---|---|---|---|
| Columns Define sheet schema and cell type (TEXT_NUMBER, DATE, CONTACT_LIST, PICKLIST, CHECKBOX); read via the API so field mappings can be generated. | Columns MySQL-compatible types mapped to fields in the paired system. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Sheets The core container; each sheet has typed columns, rows, and a modifiedAt stamp. Stacksync treats a sheet as a table and syncs its rows two-way. | Indexes Secondary indexes that keep incremental sync queries efficient. | Sheets is specific to Smartsheet and Indexes to TiDB — each maps to any object or custom field on the other side. | |
| Rows Records inside a sheet, each with createdAt/modifiedAt and cells keyed by columnId; the primary unit synced to and from external tables. | Sequences Server-side ID generation relevant when external systems write rows. | Rows is specific to Smartsheet and Sequences to TiDB — each maps to any object or custom field on the other side. | |
| Cells Row-by-column values; writes must match the column type and no single cell can exceed 4,000 characters. | Databases MySQL-style schemas addressed by any MySQL-compatible client. | Cells is specific to Smartsheet and Databases to TiDB — each maps to any object or custom field on the other side. | |
| Reports Read-only roll-ups spanning multiple sheets; pulled into a warehouse for cross-sheet reporting, capped at 50,000 rows. | Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. | Reports is specific to Smartsheet and Tables to TiDB — each maps to any object or custom field on the other side. | |
| Attachments Files linked to rows or sheets; posting one carries a 10x rate cost, so bulk file sync is throttled to 30 per minute. | Views Logical views for shaping reads before syncing outward. | Attachments is specific to Smartsheet and Views to TiDB — each maps to any object or custom field on the other side. |
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.
DetectionSmartsheet notifies Stacksync of record changes through webhook events. Sheet-scoped webhooks subscribed to *.* events notify on row and cell changes.
DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.
DetectionChanges in TiDB are captured at the source via change data capture — no polling loop against its API. Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks.
DeliveryEach detected change is written to Smartsheet through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Smartsheet–TiDB connection.
Changes in Smartsheet or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Smartsheet or TiDB data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Smartsheet or TiDB record.
Track your Smartsheet ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Smartsheet and TiDB.
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 Smartsheet and TiDB 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 Smartsheet and TiDB 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 Smartsheet and TiDB: authenticate both systems, choose the objects to sync (such as Smartsheet's Columns and Sheets), map fields visually, and changes propagate both ways in milliseconds — no code required.
Smartsheet: Cell writes must match the column type (CONTACT_LIST, PICKLIST, DATE, CHECKBOX), so mappings have to respect each column's definition. TiDB: Storage and compute scale horizontally by adding TiKV and TiDB nodes rather than resizing a single server. Stacksync's field mapping accounts for these differences between Smartsheet and TiDB 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 Smartsheet and TiDB records are not retained after a sync operation.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Smartsheet and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Smartsheet–TiDB integration in-house.
Yes — Stacksync ships production-grade connectors for both Smartsheet and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Smartsheet: Sheet-scoped webhooks subscribed to *.* events notify on row and cell changes; otherwise polling on sheet and row modifiedAt timestamps. On TiDB: Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
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 434 integrations available for Smartsheet and TiDB.