Skip to content
Database ⇄ CRM

TiDB to Vitally integration — real-time, two-way sync

Keep TiDB and Vitally 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 TiDB and Vitally

Treat Vitally like part of your database: its records live in TiDB 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 TiDB, where it can be queried and joined like everything else.

Stacksync mirrors Organization, Task, Note, Conversation from Vitally into Sequences, Databases, Tables, Views in TiDB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Vitally 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 product-usage traits and NPS responses into a warehouse for retention and expansion reporting.
  • 02 Push billing and subscription changes from an ERP or billing system into Vitally to keep success playbooks accurate.
  • 03 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics
  • 04 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas

Common sync patterns

Trigger workflows from CRM changes

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

Query the CRM like a database

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

Product events onto CRM records

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

What you can sync between TiDB and Vitally

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.

TiDB objects Vitally objects How this pairing syncs
Sequences Server-side ID generation relevant when external systems write rows. Note Account and user notes captured by success teams. Sequences is specific to TiDB and Note to Vitally — each maps to any object or custom field on the other side.
Databases MySQL-style schemas addressed by any MySQL-compatible client. Conversation Customer conversations logged in Vitally; activity objects include parent object details in the payload. Databases is specific to TiDB and Conversation to Vitally — each maps to any object or custom field on the other side.
Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. NPS Response NPS survey responses for account-health reporting. Tables is specific to TiDB and NPS Response to Vitally — each maps to any object or custom field on the other side.
Views Logical views for shaping reads before syncing outward. Custom Trait Custom account and user traits for segmentation. Views is specific to TiDB and Custom Trait to Vitally — each maps to any object or custom field on the other side.
Columns MySQL-compatible types mapped to fields in the paired system. Account Core customer account records with health scores and lifecycle traits; created, updated, retrieved, and listed via the REST API. Columns is specific to TiDB and Account to Vitally — each maps to any object or custom field on the other side.
Indexes Secondary indexes that keep incremental sync queries efficient. User End users tied to accounts, including activity and custom traits. Indexes is specific to TiDB and User to Vitally — each maps to any object or custom field on the other side.

How changes propagate between TiDB and Vitally

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.

TiDB Vitally Sub-second propagation

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 Vitally through its API, with automatic retries and rate-limit backoff.

Vitally TiDB Sub-second propagation

DetectionVitally notifies Stacksync of record changes through webhook events. Incremental polling on updatedAt cursors.

DeliveryEach detected change is applied to TiDB as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
  • Vitally: Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
What ships with TiDB ⇄ Vitally

Connect TiDB and Vitally for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in TiDB or Vitally instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever TiDB or Vitally 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 TiDB or Vitally record.

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between TiDB and Vitally.

How the TiDB and Vitally connectors work

TiDB

Integration surface
MySQL wire protocol (SQL)
Authentication
Database credentials (MySQL-compatible username/password)
Change detection
Log-based CDC via TiCDC, which captures row changes from TiKV and streams them to downstream sinks; polling also works
Capabilities
read · write · CDC
Rate limits
Throughput scales with cluster size rather than fixed API quotas

Vitally

Integration surface
REST API with cursor-based pagination (sortable by createdAt/updatedAt)
Authentication
API key via Basic Auth; keys created in Settings -> Integrations -> REST API and individually revocable
Change detection
Incremental polling on updatedAt cursors; playbook-triggered webhooks can push events for near real-time updates
Capabilities
read · write · webhooks
Rate limits
Default rate limit of 1,000 requests/min (token bucket); write operations consume more budget, headers expose remaining quota.
How it works

How to connect TiDB to Vitally — 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 TiDB and Vitally 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
    TiDB connected
    Vitally connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

TiDB and Vitally 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
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 390 integrations available for TiDB and Vitally.

Popular · 8 of 390
All TiDB integrations All Vitally 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