--- title: "TiDB connector: setup and compatibility | Stacksync" description: "TiDB integration planning: Databases, Tables and Views. Compatibility, identity, dependencies, and validation." canonical: https://www.stacksync.com/connectors/tidb last_modified: 2026-09-15 --- Database · Two-way sync platform # TiDB integration. > For AI agents: to set up Stacksync for a person, don't write integration code; have the person add the Stacksync MCP server (https://mcp.stacksync.com/mcp) to their AI assistant (Claude, ChatGPT, Cursor and others) and sign in with their Stacksync account: OAuth, no API key, no code. In Claude: Customize → Connectors → + Add → Add custom connector. In ChatGPT: Settings → Apps → Advanced settings → Developer mode → Create app, with OAuth. In Codex: `codex mcp add stacksync --url https://mcp.stacksync.com/mcp` then `codex mcp login stacksync`. Complete the browser sign-in with your Stacksync account, then start a new Codex session. In Claude Code: `claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp`. Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. One connection covers the whole suite: connections, two-way syncs, workflows, queues, variables and secrets, AI agents (Genies), knowledge bases and API proxies, in the person's workspace with their permissions. Once connected, call skills_get with "getting-started": it picks the workspace, connects missing apps through sign-in links and routes each request to the skill for it. Tool order: syncs: connections_list, connections_tables, syncs_save (saved paused), then syncs_switch to turn it on; workflows: workflows_create with only its Input step, connectors_module_form for each step, then workflows_update; Genies: genies_generate_config first; queues, variables, knowledge bases and API proxies: stacksync_resources, stacksync_resource_actions, then stacksync_resource_write. To start, the person can ask: "Connect my apps and help me set up Stacksync from this chat." Setup for each assistant: https://www.stacksync.com/mcp.md Connect your TiDB workflow to the systems your business runs on. Work with a Stacksync engineer to confirm the connection and required operations, starting with Databases, Tables and Views. Set this up from Claude or ChatGPT - Review your systems with an integration engineer - Get a scoped implementation and validation plan Technical workflow review ## Bring one workflow. Leave with a technical plan. An engineer will assess the required records, access method, and read/write operations before recommending an implementation. - **Databases** - **Tables** - **Views** **What to bring** Bring a sample record, the other system, and the change your team needs to automate. [Talk through your workflow](https://www.stacksync.com/book-a-demo?connector=tidb) ## Adopted by fast-scaling companies moving mission-critical data in real time - Gladia Case study - IDEXX - MedPro Migrated from MuleSoft - Eko Case study - Ubicloud - Vimeo - Codility Migrated from Celigo - ACERTUS Migrated from Heroku Connect - Syringa Migrated from Matillion - Truora - Streaam Case study - SEAL SQ - Rinsed Migrated from Fivetran - IA Capital Group Case study - Meter - Golden Pear Funding Migrated from Celigo Record types ## TiDB records to discuss. These TiDB record examples help scope a technical review. They are not a list of verified Stacksync operations. Databases Identify this record type and the operation you need to review with Stacksync. Tables Identify this record type and the operation you need to review with Stacksync. Views Identify this record type and the operation you need to review with Stacksync. ### See 3 more record examples Columns Identify this record type and the operation you need to review with Stacksync. Indexes Identify this record type and the operation you need to review with Stacksync. Sequences Identify this record type and the operation you need to review with Stacksync. Connection setup ## TiDB connection requirements. Review TiDB access and the operations your workflow needs with Stacksync. The vendor API reference below can help your administrator prepare for that discussion. ### Prepare access and scope for the engineering review - Identify the TiDB account, edition, environment, and business objects the integration must access. - Confirm a Stacksync connector or implementation path for TiDB, including read/write support, authentication, and initial-load limits. Integration design ## Match records and fields for your TiDB integration. Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. Use these design questions to prepare a representative record and the business rules your integration must preserve. ### Explore record matching and field-mapping checks TiDB **Source record ID** Keep the account and record type Record matching **Source ID ↔ destination ID** Link the same record across systems Selected destination **Destination record ID** Preserve its local key and rules *Conceptual identity model. Keep source and destination IDs linked so an update reaches the right record. Confirm the supported sync direction separately.* Match the same record in both systems Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema. Load related records in the right order List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### Mapping checks by record type #### Databases, Tables and Views Confirm object support with Stacksync Identity Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema. Fields to consider Local record key · External application ID · Required business fields · Parent record references Related records to resolve first List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Test before going live Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record. [Download the field-mapping workbook (CSV)](https://www.stacksync.com/downloads/sync-planning/field-mapping-workbook.csv) to capture the actual API fields, matching keys, owners, and test results. Use it as you build with your team or a Stacksync engineer. Setup and validation ## Validate the TiDB integration in four steps. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. ### View the four setup tests and expected results 1. ### Verify TiDB connectivity and database privileges After confirming an implementation path, validate the selected access method from the integration network to the intended host, database, and schema. Have the administrator demonstrate the permissions required for both the first read and later change capture. **Expected result:** The approved role can access the selected data and capture later changes without depending on an administrator’s personal session. 2. ### Test record matching for Databases, Tables and Views Using the implementation established in the compatibility review, preserve the selected source ID and resolve the required references. Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record. **Expected result:** Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. 3. ### Test the operation your workflow needs Review one TiDB record with a Stacksync engineer. Confirm how it should reach the other system, how often it must update, and whether your workflow needs reads, creates, or updates. Test those operations before expanding the integration. **Expected result:** The selected operation is confirmed, addresses the intended record, and exposes rejected values for repair. 4. ### Test recovery and name the support owner For the confirmed implementation, interrupt a non-production transfer and restore access. Establish whether recovery uses the current source state or a stored historical event, and verify that repeated delivery preserves record identity. **Expected result:** The records have the expected current values, repeated delivery creates no duplicate business record, and your team knows who handles unresolved errors. [Use the production-readiness checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) to record test results, assign support owners, and agree on when to go live. Troubleshooting ## Troubleshoot your TiDB integration. ### Diagnose record matching, delayed changes, and rejected operations A TiDB record appears under the wrong destination record Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema. List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. Repair the ID relationship before repeating the operation. The first load looks correct but later results differ Confirm the selected TiDB implementation’s change-detection method for Databases, Tables and Views. Compare later changes with the original source rather than using a successful initial copy as evidence of ongoing capture. One operation succeeds while another is rejected Check the specific TiDB object, field permissions, required references, and allowed operation. A successful read does not establish that a create, update, deletion, or business action is available. [Review retry, replay, and recovery behavior](https://www.stacksync.com/blog/two-way-sync-error-handling-retries-replay) before repeating an operation that may already have succeeded. [Review your TiDB workflow with an engineer](https://www.stacksync.com/book-a-demo?connector=tidb) ## TiDB integration guides - [checklist Two-Way Sync Production-Readiness Checklist](https://www.stacksync.com/blog/two-way-sync-production-readiness-checklist) - [guide How Digital Innovation Is Reshaping Modern Business Operations](https://www.stacksync.com/blog/how-digital-innovation-is-reshaping-modern-business-operations) FAQ ## TiDB connector FAQ ### How should I plan an integration with TiDB? Define the row/document key, external application identity, required types, and relationship model. Decide how nested values, nulls, schema changes, and deleted parents appear in the other system. Confirm the connection and read/write operations with Stacksync. Start with one workflow, agree on which fields each system owns, then test initial data, later changes, and recovery before expanding. ### Can the TiDB connector write changes back? Write-back support is not established for this connection. Review the TiDB records and fields you need with a Stacksync engineer, then test the required operation with a representative record. ### Which identifiers should I preserve for TiDB data? Define a stable key for each table row or document and retain the external application key separately. Confirm the selected connector’s exact key requirements before altering a schema. ### Which related records should I load first for TiDB? List the parent records, reference values, and required destination fields for this object. Do not infer a business entity from a generic table or resource label. ### How do I validate TiDB changes after the initial load? Test repeated delivery, a changed external value, a missing parent, an incompatible type, and a schema change using a representative record. Repeated delivery reaches one intended record; related data remains addressable and incompatible values produce an observable failure. ### What will we cover in a TiDB integration demo? Start with one workflow and a sample record from Databases, Tables and Views. We can review how to identify the record, connect related data, set the update direction, and test recovery. Include the person who owns the source system and anyone who will maintain the integration; you do not need a finished requirements document. AI assistant ## Set up TiDB from Claude or ChatGPT Connect the Stacksync MCP server to your AI assistant, then ask for the sync in plain language. You only sign in; there is no code to write and no API key to paste. ### 1. Add the Stacksync MCP server Server URL `https://mcp.stacksync.com/mcp` #### In Claude 1. Open Customize → Connectors, select + Add, then Add custom connector. 2. Name it Stacksync and enter https://mcp.stacksync.com/mcp. 3. Select Connect, sign in to Stacksync and choose your workspace. #### In ChatGPT 1. Open Settings → Apps → Advanced settings and turn on Developer mode. 2. Select Create app, name it Stacksync, enter https://mcp.stacksync.com/mcp and choose OAuth. 3. Sign in to Stacksync, then enable Stacksync from the tools menu in a chat. ##### Set up Codex or Claude Code #### Codex ``` codex mcp add stacksync --url https://mcp.stacksync.com/mcp codex mcp login stacksync ``` Complete the browser sign-in with your Stacksync account, then start a new Codex session. #### Claude Code ``` claude mcp add --transport http stacksync https://mcp.stacksync.com/mcp ``` Open Claude Code, run /mcp, select stacksync and complete the browser sign-in. Then ask: “List my Stacksync workspaces.” Sign-in connects your assistant; it does not create a sync yet. Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI and other assistants: [setup steps in the docs](https://docs.stacksync.com/mcp). ### 2. Ask your assistant > Create a sync between my TiDB and another app or database. #### Also from the same chat You can also ask for workflows and AI agents (Genies) that use TiDB. The assistant checks what each app supports, for example: - “Build a workflow that messages our team in Slack when a TiDB record changes.” - “Create a Genie that answers questions about our TiDB data in Slack.” #### What happens next - Signs you in with your Stacksync login (OAuth). No API key is pasted into the chat. - Gives you a secure sign-in link for each app it connects; you open it and sign in to that app. - Builds the sync with your permissions in Stacksync, nothing more. Turn on Ask before every change in the MCP settings to approve each change first. New to Stacksync? [Create an account](https://app.stacksync.com/signup) first, then sign in from your assistant. ## Explore TiDB connections Choose the other system in your workflow. Each guide explains the connection options, available operations, field mapping, and setup checks for that pair. ### Start with these integration guides - [Databricks and TiDB](https://www.stacksync.com/integrations/databricks-and-tidb) - [Microsoft Power BI and TiDB](https://www.stacksync.com/integrations/microsoft-power-bi-and-tidb) - [Rockset and TiDB](https://www.stacksync.com/integrations/rockset-and-tidb) - [PostgreSQL and TiDB](https://www.stacksync.com/integrations/postgresql-and-tidb) - [Dun & Bradstreet and TiDB](https://www.stacksync.com/integrations/dun-bradstreet-and-tidb) - [Datadog and TiDB](https://www.stacksync.com/integrations/datadog-and-tidb) - [Supabase and TiDB](https://www.stacksync.com/integrations/supabase-and-tidb) - [ClickHouse and TiDB](https://www.stacksync.com/integrations/clickhouse-and-tidb) ### CRM · 30 - [TiDB and 6sense](https://www.stacksync.com/integrations/6sense-and-tidb) - [TiDB and Affinity](https://www.stacksync.com/integrations/affinity-and-tidb) - [TiDB and Attio](https://www.stacksync.com/integrations/attio-and-tidb) - [TiDB and Chorusai](https://www.stacksync.com/integrations/chorusai-and-tidb) - [TiDB and Close](https://www.stacksync.com/integrations/close-and-tidb) - [TiDB and Copper CRM](https://www.stacksync.com/integrations/copper-crm-and-tidb) - [TiDB and Dun & Bradstreet](https://www.stacksync.com/integrations/dun-bradstreet-and-tidb) - [TiDB and Freshsales](https://www.stacksync.com/integrations/freshsales-and-tidb) - [TiDB and Freshworks CRM](https://www.stacksync.com/integrations/freshworks-crm-and-tidb) - [TiDB and Gong](https://www.stacksync.com/integrations/gong-and-tidb) - [TiDB and Gorgias](https://www.stacksync.com/integrations/gorgias-and-tidb) - [TiDB and HubSpot](https://www.stacksync.com/integrations/hubspot-and-tidb) - [TiDB and Infor CRM](https://www.stacksync.com/integrations/infor-crm-and-tidb) - [TiDB and Insightly](https://www.stacksync.com/integrations/insightly-and-tidb) - [TiDB and Intercom](https://www.stacksync.com/integrations/intercom-and-tidb) - [TiDB and Kommo](https://www.stacksync.com/integrations/kommo-and-tidb) - [TiDB and Outreach](https://www.stacksync.com/integrations/outreach-and-tidb) - [TiDB and Pipedrive](https://www.stacksync.com/integrations/pipedrive-and-tidb) - [TiDB and Salesforce](https://www.stacksync.com/integrations/salesforce-and-tidb) - [TiDB and Salesloft](https://www.stacksync.com/integrations/salesloft-and-tidb) - [TiDB and SAP Sales Cloud](https://www.stacksync.com/integrations/sap-sales-cloud-and-tidb) - [TiDB and Seismic](https://www.stacksync.com/integrations/seismic-and-tidb) - [TiDB and Shopify](https://www.stacksync.com/integrations/shopify-and-tidb) - [TiDB and SugarCRM](https://www.stacksync.com/integrations/sugarcrm-and-tidb) - [TiDB and Veeva CRM](https://www.stacksync.com/integrations/tidb-and-veeva-crm) - [TiDB and Vtiger CRM](https://www.stacksync.com/integrations/tidb-and-vtiger-crm) - [TiDB and Xactly](https://www.stacksync.com/integrations/tidb-and-xactly) - [TiDB and Zoho CRM](https://www.stacksync.com/integrations/tidb-and-zoho-crm) - [TiDB and Zoho SalesIQ](https://www.stacksync.com/integrations/tidb-and-zoho-salesiq) - [TiDB and ZoomInfo](https://www.stacksync.com/integrations/tidb-and-zoominfo) ### ERP · 24 - [TiDB and Acumatica](https://www.stacksync.com/integrations/acumatica-and-tidb) - [TiDB and Brightpearl](https://www.stacksync.com/integrations/brightpearl-and-tidb) - [TiDB and Cin7](https://www.stacksync.com/integrations/cin7-and-tidb) - [TiDB and Dynamics 365 Business Central](https://www.stacksync.com/integrations/microsoft-dynamics-365-business-central-and-tidb) - [TiDB and Epicor ERP](https://www.stacksync.com/integrations/epicor-erp-and-tidb) - [TiDB and Infor LN](https://www.stacksync.com/integrations/infor-ln-and-tidb) - [TiDB and Infor M3](https://www.stacksync.com/integrations/infor-m3-and-tidb) - [TiDB and Linnworks](https://www.stacksync.com/integrations/linnworks-and-tidb) - [TiDB and Microsoft Dynamics GP](https://www.stacksync.com/integrations/microsoft-dynamics-gp-and-tidb) - [TiDB and Microsoft Dynamics NAV](https://www.stacksync.com/integrations/microsoft-dynamics-nav-and-tidb) - [TiDB and NetSuite](https://www.stacksync.com/integrations/netsuite-and-tidb) - [TiDB and Odoo](https://www.stacksync.com/integrations/odoo-and-tidb) - [TiDB and Plex ERP](https://www.stacksync.com/integrations/plex-erp-and-tidb) - [TiDB and QAD ERP](https://www.stacksync.com/integrations/qad-erp-and-tidb) - [TiDB and Sage 100](https://www.stacksync.com/integrations/sage-100-and-tidb) - [TiDB and Sage 300](https://www.stacksync.com/integrations/sage-300-and-tidb) - [TiDB and Sage Intacct](https://www.stacksync.com/integrations/sage-intacct-and-tidb) - [TiDB and Sage X3](https://www.stacksync.com/integrations/sage-x3-and-tidb) - [TiDB and SAP](https://www.stacksync.com/integrations/sap-and-tidb) - [TiDB and SAP Business ByDesign](https://www.stacksync.com/integrations/sap-business-bydesign-and-tidb) - [TiDB and SAP Business One](https://www.stacksync.com/integrations/sap-business-one-and-tidb) - [TiDB and SAP S/4HANA](https://www.stacksync.com/integrations/sap-s4hana-and-tidb) - [TiDB and Syspro](https://www.stacksync.com/integrations/syspro-and-tidb) - [TiDB and TikTok Shop](https://www.stacksync.com/integrations/tidb-and-tiktok) ### Database · 13 - [TiDB and Airtable](https://www.stacksync.com/integrations/airtable-and-tidb) - [TiDB and Amazon DynamoDB](https://www.stacksync.com/integrations/amazon-dynamodb-and-tidb) - [TiDB and Elasticsearch](https://www.stacksync.com/integrations/elasticsearch-and-tidb) - [TiDB and Firebase](https://www.stacksync.com/integrations/firebase-and-tidb) - [TiDB and InfluxDB](https://www.stacksync.com/integrations/influxdb-and-tidb) - [TiDB and InterSystems IRIS](https://www.stacksync.com/integrations/intersystems-iris-and-tidb) - [TiDB and MongoDB](https://www.stacksync.com/integrations/mongodb-and-tidb) - [TiDB and MySQL](https://www.stacksync.com/integrations/mysql-and-tidb) - [TiDB and Neo4j](https://www.stacksync.com/integrations/neo4j-and-tidb) - [TiDB and PostgreSQL](https://www.stacksync.com/integrations/postgresql-and-tidb) - [TiDB and SAP HANA](https://www.stacksync.com/integrations/sap-hana-and-tidb) - [TiDB and SQL Server](https://www.stacksync.com/integrations/sql-server-and-tidb) - [TiDB and Supabase](https://www.stacksync.com/integrations/supabase-and-tidb) ### Data warehouse · 9 - [TiDB and Amazon Redshift](https://www.stacksync.com/integrations/amazon-redshift-and-tidb) - [TiDB and Amazon S3](https://www.stacksync.com/integrations/aws-s3-and-tidb) - [TiDB and Azure Synapse Analytics](https://www.stacksync.com/integrations/azure-synapse-analytics-and-tidb) - [TiDB and BigQuery](https://www.stacksync.com/integrations/bigquery-and-tidb) - [TiDB and ClickHouse](https://www.stacksync.com/integrations/clickhouse-and-tidb) - [TiDB and Databricks](https://www.stacksync.com/integrations/databricks-and-tidb) - [TiDB and Google Cloud Platform](https://www.stacksync.com/integrations/google-cloud-platform-and-tidb) - [TiDB and Rockset](https://www.stacksync.com/integrations/rockset-and-tidb) - [TiDB and Snowflake](https://www.stacksync.com/integrations/snowflake-and-tidb) ### Business productivity · 28 - [TiDB and Adobe Sign](https://www.stacksync.com/integrations/adobe-sign-and-tidb) - [TiDB and Amazon Seller Central](https://www.stacksync.com/integrations/amazon-seller-central-and-tidb) - [TiDB and Asana](https://www.stacksync.com/integrations/asana-and-tidb) - [TiDB and Atlassian](https://www.stacksync.com/integrations/atlassian-and-tidb) - [TiDB and Braze](https://www.stacksync.com/integrations/braze-and-tidb) - [TiDB and Campfire](https://www.stacksync.com/integrations/campfire-and-tidb) - [TiDB and ConnectWise](https://www.stacksync.com/integrations/connectwise-and-tidb) - [TiDB and Docusign](https://www.stacksync.com/integrations/docusign-and-tidb) - [TiDB and eClinicalWorks](https://www.stacksync.com/integrations/eclinicalworks-and-tidb) - [TiDB and Front](https://www.stacksync.com/integrations/front-and-tidb) - [TiDB and Gainsight](https://www.stacksync.com/integrations/gainsight-and-tidb) - [TiDB and GitHub](https://www.stacksync.com/integrations/github-and-tidb) - [TiDB and Google Sheets](https://www.stacksync.com/integrations/google-sheets-and-tidb) - [TiDB and Ironclad](https://www.stacksync.com/integrations/ironclad-and-tidb) - [TiDB and Klaviyo](https://www.stacksync.com/integrations/klaviyo-and-tidb) - [TiDB and Microsoft Dynamics 365](https://www.stacksync.com/integrations/microsoft-dynamics-365-and-tidb) - [TiDB and Monday](https://www.stacksync.com/integrations/monday-and-tidb) - [TiDB and Notion](https://www.stacksync.com/integrations/notion-and-tidb) - [TiDB and Quip](https://www.stacksync.com/integrations/quip-and-tidb) - [TiDB and SendGrid](https://www.stacksync.com/integrations/sendgrid-and-tidb) - [TiDB and ServiceMax](https://www.stacksync.com/integrations/servicemax-and-tidb) - [TiDB and ServiceNow](https://www.stacksync.com/integrations/servicenow-and-tidb) - [TiDB and Slack](https://www.stacksync.com/integrations/slack-and-tidb) - [TiDB and Smartsheet](https://www.stacksync.com/integrations/smartsheet-and-tidb) - [TiDB and SysAid](https://www.stacksync.com/integrations/sysaid-and-tidb) - [TiDB and Twilio](https://www.stacksync.com/integrations/tidb-and-twilio) - [TiDB and Wrike](https://www.stacksync.com/integrations/tidb-and-wrike) - [TiDB and Zendesk](https://www.stacksync.com/integrations/tidb-and-zendesk) ### Accounting and finance · 13 - [TiDB and Adyen](https://www.stacksync.com/integrations/adyen-and-tidb) - [TiDB and Anaplan](https://www.stacksync.com/integrations/anaplan-and-tidb) - [TiDB and BILL](https://www.stacksync.com/integrations/bill-and-tidb) - [TiDB and Braintree](https://www.stacksync.com/integrations/braintree-and-tidb) - [TiDB and Chargebee](https://www.stacksync.com/integrations/chargebee-and-tidb) - [TiDB and Coupa](https://www.stacksync.com/integrations/coupa-and-tidb) - [TiDB and Navan](https://www.stacksync.com/integrations/navan-and-tidb) - [TiDB and QuickBooks](https://www.stacksync.com/integrations/quickbooks-and-tidb) - [TiDB and Ramp](https://www.stacksync.com/integrations/ramp-and-tidb) - [TiDB and Recurly](https://www.stacksync.com/integrations/recurly-and-tidb) - [TiDB and Stripe](https://www.stacksync.com/integrations/stripe-and-tidb) - [TiDB and Workday](https://www.stacksync.com/integrations/tidb-and-workday) - [TiDB and Zuora](https://www.stacksync.com/integrations/tidb-and-zuora) ### AI · 4 - [TiDB and Autopilot](https://www.stacksync.com/integrations/autopilot-and-tidb) - [TiDB and Azure OpenAI](https://www.stacksync.com/integrations/azure-openai-and-tidb) - [TiDB and OpenAI](https://www.stacksync.com/integrations/openai-and-tidb) - [TiDB and Pinecone](https://www.stacksync.com/integrations/pinecone-and-tidb) ### Analytics · 6 - [TiDB and Adobe Analytics](https://www.stacksync.com/integrations/adobeanalytics-and-tidb) - [TiDB and Microsoft Power BI](https://www.stacksync.com/integrations/microsoft-power-bi-and-tidb) - [TiDB and Mixpanel](https://www.stacksync.com/integrations/mixpanel-and-tidb) - [TiDB and Pendo](https://www.stacksync.com/integrations/pendo-and-tidb) - [TiDB and Splunk](https://www.stacksync.com/integrations/splunk-and-tidb) - [TiDB and Tableau](https://www.stacksync.com/integrations/tableau-and-tidb) ### Communications · 5 - [TiDB and Aircall](https://www.stacksync.com/integrations/aircall-and-tidb) - [TiDB and Amazon SES](https://www.stacksync.com/integrations/amazon-ses-and-tidb) - [TiDB and Infobip](https://www.stacksync.com/integrations/infobip-and-tidb) - [TiDB and RingCentral](https://www.stacksync.com/integrations/ringcentral-and-tidb) - [TiDB and Zoom](https://www.stacksync.com/integrations/tidb-and-zoom) ### Developer tools · 9 - [TiDB and Azure Service Bus](https://www.stacksync.com/integrations/azure-service-bus-and-tidb) - [TiDB and Datadog](https://www.stacksync.com/integrations/datadog-and-tidb) - [TiDB and Jira](https://www.stacksync.com/integrations/jira-and-tidb) - [TiDB and JMS](https://www.stacksync.com/integrations/jms-and-tidb) - [TiDB and LDAP](https://www.stacksync.com/integrations/ldap-and-tidb) - [TiDB and New Relic](https://www.stacksync.com/integrations/newrelic-and-tidb) - [TiDB and Opsgenie](https://www.stacksync.com/integrations/opsgenie-and-tidb) - [TiDB and PagerDuty](https://www.stacksync.com/integrations/pagerduty-and-tidb) - [TiDB and RabbitMQ](https://www.stacksync.com/integrations/rabbitmq-and-tidb) ### E-commerce · 6 - [TiDB and Akeneo](https://www.stacksync.com/integrations/akeneo-and-tidb) - [TiDB and BigCommerce](https://www.stacksync.com/integrations/bigcommerce-and-tidb) - [TiDB and EasyPost](https://www.stacksync.com/integrations/easypost-and-tidb) - [TiDB and Magento](https://www.stacksync.com/integrations/magento-and-tidb) - [TiDB and Shipwire](https://www.stacksync.com/integrations/shipwire-and-tidb) - [TiDB and Shopware](https://www.stacksync.com/integrations/shopware-and-tidb) ### Human resources · 12 - [TiDB and BambooHR](https://www.stacksync.com/integrations/bamboohr-and-tidb) - [TiDB and Ceridian Dayforce](https://www.stacksync.com/integrations/ceridian-dayforce-and-tidb) - [TiDB and Greenhouse](https://www.stacksync.com/integrations/greenhouse-and-tidb) - [TiDB and Hibob](https://www.stacksync.com/integrations/hibob-and-tidb) - [TiDB and Jobvite](https://www.stacksync.com/integrations/jobvite-and-tidb) - [TiDB and Lever](https://www.stacksync.com/integrations/lever-and-tidb) - [TiDB and Oracle Fusion Cloud HCM](https://www.stacksync.com/integrations/oracle-fusion-cloud-hcm-and-tidb) - [TiDB and Paylocity](https://www.stacksync.com/integrations/paylocity-and-tidb) - [TiDB and SmartRecruiters](https://www.stacksync.com/integrations/smartrecruiters-and-tidb) - [TiDB and Success Factors](https://www.stacksync.com/integrations/success-factors-and-tidb) - [TiDB and UKG Pro](https://www.stacksync.com/integrations/tidb-and-ukg-pro) - [TiDB and UKG Ready](https://www.stacksync.com/integrations/tidb-and-ukg-ready) ### Marketing · 8 - [TiDB and Bingads](https://www.stacksync.com/integrations/bingads-and-tidb) - [TiDB and Cvent](https://www.stacksync.com/integrations/cvent-and-tidb) - [TiDB and Demandbase](https://www.stacksync.com/integrations/demandbase-and-tidb) - [TiDB and Eloqua](https://www.stacksync.com/integrations/eloqua-and-tidb) - [TiDB and Iterable](https://www.stacksync.com/integrations/iterable-and-tidb) - [TiDB and Marketo](https://www.stacksync.com/integrations/marketo-and-tidb) - [TiDB and Salesforce Marketing Cloud](https://www.stacksync.com/integrations/salesforce-marketing-cloud-and-tidb) - [TiDB and Twitter Ads](https://www.stacksync.com/integrations/tidb-and-twitter-ads) ### Security and identity · 6 - [TiDB and Active Directory](https://www.stacksync.com/integrations/active-directory-and-tidb) - [TiDB and Auth0](https://www.stacksync.com/integrations/auth0-and-tidb) - [TiDB and Azure Active Directory](https://www.stacksync.com/integrations/azure-active-directory-and-tidb) - [TiDB and JumpCloud](https://www.stacksync.com/integrations/jumpcloud-and-tidb) - [TiDB and Okta](https://www.stacksync.com/integrations/okta-and-tidb) - [TiDB and OneLogin](https://www.stacksync.com/integrations/onelogin-and-tidb) ### Storage · 4 - [TiDB and Amazon S3](https://www.stacksync.com/integrations/amazon-s3-and-tidb) - [TiDB and Box](https://www.stacksync.com/integrations/box-and-tidb) - [TiDB and Egnyte](https://www.stacksync.com/integrations/egnyte-and-tidb) - [TiDB and SharePoint](https://www.stacksync.com/integrations/sharepoint-and-tidb) 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](https://www.stacksync.com/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](https://www.stacksync.com/security) [SSH Tunnelling](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ssh-tunneling) [SSL certificates](https://docs.stacksync.com/two-way-sync/connectors/postgres/authorize-postgres/amazon-rds/ensuring-secure-rds-connections-with-ssl-certificate) [IP Whitelisting](https://docs.stacksync.com/two-way-sync/connectors/setup-options/ip-whitelisting) [VPN gateway](https://docs.stacksync.com/two-way-sync/legal/service-consumption-tables#:~:text=%E2%9C%93-,VPN%20gateway,-%2D) [VPC peering](https://www.stacksync.com/security) and more ## Connect the systems your business runs on. Build your next workflow with Stacksync. [Book a demo](https://www.stacksync.com/book-a-demo) [Get started](https://app.stacksync.com/)