Skip to content
Business productivity ⇄ Database

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

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

Mirror Sysaid'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 Sysaid 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 Companies, Custom Fields, Incidents, Service Requests from Sysaid into Indexes, Sequences, Databases, Tables 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 Sysaid, so the tool and the database never disagree.

Common use cases

  • 01 Sync Users, Groups, and Companies from an HRIS or identity provider so requester and agent records, departments, and managers stay current in SysAid.
  • 02 Mirror Assets and Configuration Items with an external CMDB or asset database so inventory and ticket linkage share one source of truth.
  • 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

Read Sysaid with a query

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

Automate Sysaid from your codebase

Write to the synced tables in TiDB and Stacksync propagates the change into Sysaid, replacing custom integration code.

React to changes as they happen

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

What you can sync between Sysaid 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.

Sysaid objects TiDB objects How this pairing syncs
Service Requests Catalog and help-desk requests on the same /sr endpoint (type=request); written or read so fulfillment can be driven from another system. Sequences Server-side ID generation relevant when external systems write rows. Service Requests is specific to Sysaid and Sequences to TiDB — each maps to any object or custom field on the other side.
Problems Root-cause records that group related incidents; read and written to keep problem management aligned with an external ITSM or reporting store. Databases MySQL-style schemas addressed by any MySQL-compatible client. Problems is specific to Sysaid and Databases to TiDB — each maps to any object or custom field on the other side.
Changes Change records (type=change) with approval and scheduling fields; synced two-way to drive CAB review and deployment workflows. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Changes is specific to Sysaid and Tables to TiDB — each maps to any object or custom field on the other side.
Users End users and admins on the /users endpoint; synced with an HRIS or identity source to keep requester and agent records current. Views Logical views for shaping reads before syncing outward. Users is specific to Sysaid and Views to TiDB — each maps to any object or custom field on the other side.
Assets Hardware and software inventory; read out to a warehouse or written from a discovery or CMDB source of truth. Columns MySQL-compatible types mapped to fields in the paired system. Assets is specific to Sysaid and Columns to TiDB — each maps to any object or custom field on the other side.
Configuration Items (CIs) CMDB entries and their relationships; synced with an external CMDB or asset database for one inventory view. Indexes Secondary indexes that keep incremental sync queries efficient. Configuration Items (CIs) is specific to Sysaid and Indexes to TiDB — each maps to any object or custom field on the other side.

How changes propagate between Sysaid 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.

Sysaid TiDB Sub-second propagation

DetectionSysaid notifies Stacksync of record changes through webhook events. Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature.

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

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

Rate-limit considerations

  • Sysaid: Requests are throttled per the X-RateLimit-Limit / -Remaining / -Reset headers; list calls are paginated with a limit parameter and each org is capped at 100 application keys.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Sysaid ⇄ TiDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Sysaid and TiDB connectors work

Sysaid

Integration surface
REST API (JSON)
Authentication
Client-credentials app keys: an application key (clientId/clientSecret) is created via /v1/application-keys, then exchanged at /v1/access-tokens for a bearer token (default 24h, up to 30 days); an x-sysaid-accountid header scopes the account. Legacy V0 uses session-cookie login.
Change detection
Webhooks (beta) push sr.created and sr.updated events with changed-field diffs and an X-Sysaid-Signature; otherwise poll the /sr endpoint filtering on update_time.gte.
Capabilities
read · write · webhooks
Rate limits
Requests are throttled per the X-RateLimit-Limit / -Remaining / -Reset headers; list calls are paginated with a limit parameter and each org is capped at 100 application keys.

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 Sysaid 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 Sysaid 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
    Sysaid connected
    TiDB connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Sysaid 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.

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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 434 integrations available for Sysaid and TiDB.

Popular · 6 of 434
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.