Skip to content
Business productivity ⇄ Database

Full Enrich to TiDB integration — real-time, two-way sync

Keep Full Enrich 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.

  • 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 Full Enrich and TiDB

Mirror Full Enrich's data into TiDB so your own code can read and write it like any other table, with changes flowing both ways in seconds.

Engineers integrate with tools like Full Enrich 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 Phone numbers, Credits, Enrichment requests, Contacts from Full Enrich into Sequences, Databases, Tables, Views 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 Full Enrich, so the tool and the database never disagree.

Common use cases

  • 01 Route enrichment completions via webhook into a database that keeps contactability status current.
  • 02 Enrich new CRM contacts with verified emails and mobile numbers as they are created.
  • 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

React to changes as they happen

Updates in Full Enrich arrive as row changes in TiDB, so triggers, jobs, and services can respond in near real time.

One integration pattern for the whole stack

Every synced tool looks the same from the database, so each new integration is configuration, not a new codebase.

Read Full Enrich with a query

Records from Full Enrich are ordinary rows in TiDB; join them, index them, and use them in application logic without touching the vendor API.

What you can sync between Full Enrich and TiDB

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.

Full Enrich objects TiDB objects How this pairing syncs
Contacts The person inputs (name plus company or domain) sent for enrichment. Databases MySQL-style schemas addressed by any MySQL-compatible client. Contacts is specific to Full Enrich and Databases to TiDB — each maps to any object or custom field on the other side.
Enrichment results Completed records fetched by request ID or delivered via webhook. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Enrichment results is specific to Full Enrich and Tables to TiDB — each maps to any object or custom field on the other side.
Emails Returned addresses with verification status, written back to the CRM or database. Views Logical views for shaping reads before syncing outward. Emails is specific to Full Enrich and Views to TiDB — each maps to any object or custom field on the other side.
Phone numbers Returned mobile and direct-dial numbers from the provider waterfall. Columns MySQL-compatible types mapped to fields in the paired system. Phone numbers is specific to Full Enrich and Columns to TiDB — each maps to any object or custom field on the other side.
Credits Account balance consumed on successful finds; monitored to pace sync jobs. Indexes Secondary indexes that keep incremental sync queries efficient. Credits is specific to Full Enrich and Indexes to TiDB — each maps to any object or custom field on the other side.
Enrichment requests Submitted batches of contacts to enrich; processed asynchronously by the waterfall. Sequences Server-side ID generation relevant when external systems write rows. Enrichment requests is specific to Full Enrich and Sequences to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Full Enrich and TiDB

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.

Full Enrich TiDB Sub-second propagation

DetectionFull Enrich notifies Stacksync of record changes through webhook events. Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback.

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

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

Rate-limit considerations

  • Full Enrich: Subject to the platform's API rate limits and per-batch size constraints.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Full Enrich ⇄ TiDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Full Enrich and TiDB connectors work

Full Enrich

Integration surface
REST API with asynchronous bulk enrichment endpoints
Authentication
API key (Bearer token)
Change detection
Webhook callbacks when enrichment batches complete, with polling of result endpoints as a fallback
Capabilities
read · write · webhooks
Rate limits
Subject to the platform's API rate limits and per-batch size constraints

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
How it works

How to connect Full Enrich to TiDB — 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 Full Enrich 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.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Full Enrich connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Full Enrich 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Full Enrich ⇄ TiDB
    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
    Full Enrich TiDB
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Full Enrich and TiDB 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 311 integrations available for Full Enrich and TiDB.

Popular · 7 of 311
All Full Enrich integrations All TiDB 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