Two-way sync
Changes in Sysaid or TiDB instantly reflect in both systems. No stale data, no manual imports.
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.
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.
Records from Sysaid are ordinary rows in TiDB; join them, index them, and use them in application logic without touching the vendor API.
Write to the synced tables in TiDB and Stacksync propagates the change into Sysaid, replacing custom integration code.
Updates in Sysaid arrive as row changes in TiDB, so triggers, jobs, and services can respond in near real time.
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. |
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.
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.
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.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Sysaid–TiDB connection.
Changes in Sysaid or TiDB instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Sysaid 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 Sysaid or TiDB record.
Track your Sysaid ⇄ TiDB sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Sysaid 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 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.
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.
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 Sysaid and TiDB: authenticate both systems, choose the objects to sync (such as Sysaid's Service Requests and Problems), map fields visually, and changes propagate both ways in milliseconds — no code required.
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Sysaid and TiDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Sysaid–TiDB integration in-house.
Yes — Stacksync ships production-grade connectors for both Sysaid and TiDB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
Change detection on Sysaid: 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. 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.
On the Sysaid side: Companies, Custom Fields, Incidents, Service Requests, plus custom fields where Sysaid exposes them. On the TiDB side: Indexes, Sequences, Databases, Tables. Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 Sysaid and TiDB.