Skip to content
Database ⇄ Accounting and finance

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

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

Work with Zuora's financial data straight from TiDB: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Usage, Order and Amendment, Account (Billing Account), Subscription from Zuora into Views, Columns, Indexes, Sequences in TiDB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against TiDB, and rows your code writes or updates flow back into Zuora with validation, so the finance system stays the system of record.

Common use cases

  • 01 Stream metered Usage records from a warehouse or metering pipeline into Zuora so consumption-based charges are rated on the correct Rate Plan.
  • 02 Two-way sync of Accounts and Subscriptions with an operational Postgres database so product and finance teams read billing state in SQL while changes flow back into Zuora.
  • 03 Serve mixed transactional and analytical workloads on synced data using TiFlash columnar replicas
  • 04 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge

Common sync patterns

Query finance data like any other data

Customers, invoices, and payments from Zuora live in TiDB as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on TiDB; Stacksync handles the API calls, rate limits, and retries against Zuora.

Write back safely

Updates written to the synced tables in TiDB propagate into Zuora, so automations can create or correct finance records without custom integration code.

What you can sync between TiDB and Zuora

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 Zuora objects How this pairing syncs
Views Logical views for shaping reads before syncing outward. Invoice Billing documents generated from rate plan charges and order line items; typically read out into an ERP or GL for revenue recognition and reconciliation. Views is specific to TiDB and Invoice to Zuora — each maps to any object or custom field on the other side.
Columns MySQL-compatible types mapped to fields in the paired system. Payment Payment and refund transactions applied against invoices; read for cash application, dunning, and reconciliation reporting in the warehouse. Columns is specific to TiDB and Payment to Zuora — each maps to any object or custom field on the other side.
Indexes Secondary indexes that keep incremental sync queries efficient. Usage Metered consumption records; written into Zuora from a metering or warehouse pipeline so consumption-based charges are rated and invoiced. Indexes is specific to TiDB and Usage to Zuora — each maps to any object or custom field on the other side.
Sequences Server-side ID generation relevant when external systems write rows. Order and Amendment Records of subscription create and change actions; written to Zuora to drive quote-to-cash and read for subscription change history. Sequences is specific to TiDB and Order and Amendment to Zuora — each maps to any object or custom field on the other side.
Databases MySQL-style schemas addressed by any MySQL-compatible client. Account (Billing Account) The customer billing entity holding contacts, payment methods, and billing settings; synced two-way as the parent record most other Zuora objects hang off. Databases is specific to TiDB and Account (Billing Account) to Zuora — 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. Subscription Recurring or usage-based subscription tied to an Account; read for revenue state and written when provisioning or changing plans from a CRM or app. Tables is specific to TiDB and Subscription to Zuora — each maps to any object or custom field on the other side.

How changes propagate between TiDB and Zuora

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

Zuora TiDB Sub-second propagation

DetectionZuora notifies Stacksync of record changes through webhook events. Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for.

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.
  • Zuora: Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
What ships with TiDB ⇄ Zuora

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your TiDB ⇄ Zuora 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 Zuora.

How the TiDB and Zuora 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

Zuora

Integration surface
REST API (v1) with Object Query, Data Query, and AQuA bulk export; legacy SOAP API also available
Authentication
OAuth 2.0 client credentials (bearer token, 3600s expiry); access is governed by the Zuora role of the OAuth client's associated user, with no granular scopes
Change detection
Incremental extraction on the indexed UpdatedDate column via ZOQL/AQuA stateful mode (high-water mark), plus Callout Notifications (webhooks) for event-driven changes
Capabilities
read · write · webhooks
Rate limits
Concurrency limits: 40 concurrent requests by default, 80 for Object Queries, 200 for high-volume operations (doubled for Performance Booster); HTTP 429 on breach with exponential backoff; OAuth token endpoint is not bound by the limit.
How it works

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

    Choose tables

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

TiDB and Zuora 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 424 integrations available for TiDB and Zuora.

Popular · 8 of 424
All TiDB integrations All Zuora 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