Skip to content
Communications ⇄ Database

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

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

Turn the messages, calls, and events Aircall handles into live rows in TiDB, and write back to trigger new outbound communication, with both sides in sync in seconds.

Engineers reach communications tools like Aircall through APIs, which means auth tokens, webhooks, delivery callbacks, and rate limits, all maintained forever and all shaped differently for every tool. The data those tools produce, who was contacted, what was sent, and what came back, would be simple to use if it lived in TiDB next to everything else.

Stacksync mirrors Teams, Messages (SMS/MMS), Webhooks, Contacts from Aircall into Tables, Views, Columns, Indexes in TiDB and keeps both sides in sync in real time. Communication activity lands in the database as ordinary rows you can query and join, and rows your code writes, such as a queued outbound message or an updated contact, flow back into Aircall so the tool and the database never disagree.

There is no webhook endpoint to host, no rate limit to babysit, and no nightly export that leaves your services reading yesterday's activity.

Common use cases

  • 01 Send outbound SMS/MMS through the Messages API when a CRM or database record changes (appointment reminders, alerts) and write inbound replies back.
  • 02 Sync Tags and call dispositions onto matching CRM records as call outcomes so RevOps can report on conversation activity.
  • 03 Two-way sync between TiDB tables and SaaS tools so operational edits made in either system converge
  • 04 Stream row-level changes to a warehouse or Kafka via CDC for near-real-time analytics

Common sync patterns

Communication history as database rows

Every message, call, or event Aircall records becomes rows in TiDB, ready to query, join with your own data, and report on without touching the vendor API.

Trigger outbound communication from the database

Write a row to a synced table in TiDB and Stacksync propagates it into Aircall, so your code sends the message, places the call, or schedules the meeting without integration glue.

One contact list across both

Recipients and contacts stay consistent between Aircall and TiDB, so a phone number or email corrected on either side is current the next time either system uses it.

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

Aircall objects TiDB objects How this pairing syncs
Webhooks Event subscriptions for call, contact, user, message, and number events; full CRUD, the mechanism for near-real-time change delivery to Stacksync. Tables Row data stored in TiKV; the primary unit for reads, writes, and CDC. Webhooks is specific to Aircall and Tables to TiDB — each maps to any object or custom field on the other side.
Contacts Shared and personal phone-book contacts with full CRUD plus search by phone number or email; the primary two-way object synced with CRM contacts for click-to-dial. Views Logical views for shaping reads before syncing outward. Contacts is specific to Aircall and Views to TiDB — each maps to any object or custom field on the other side.
Calls Inbound and outbound call records with recording URL, duration, tags, comments, and metadata; the record itself is read-only, but you can add tags, comments, insight cards, transfer, archive, and control recording. Columns MySQL-compatible types mapped to fields in the paired system. Calls is specific to Aircall and Columns to TiDB — each maps to any object or custom field on the other side.
Users Agent seats with name, email, and availability; full CRUD to provision or deprovision seats and map Aircall agents to CRM, HR, or directory identities. Indexes Secondary indexes that keep incremental sync queries efficient. Users is specific to Aircall and Indexes to TiDB — each maps to any object or custom field on the other side.
Numbers Provisioned phone numbers with settings, open hours, and IVR config; read and update to keep routing and business-hours data aligned across systems. Sequences Server-side ID generation relevant when external systems write rows. Numbers is specific to Aircall and Sequences to TiDB — each maps to any object or custom field on the other side.
Tags Call tags with name and color; full CRUD, applied to calls for disposition and outcome reporting in the CRM or warehouse. Databases MySQL-style schemas addressed by any MySQL-compatible client. Tags is specific to Aircall and Databases to TiDB — each maps to any object or custom field on the other side.

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

Aircall TiDB Sub-second propagation

DetectionAircall notifies Stacksync of record changes through webhook events. Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events.

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

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

Rate-limit considerations

  • Aircall: 60 requests per minute per company by default (120/min for Advanced Messaging customers); responses carry X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers.
  • TiDB: Throughput scales with cluster size rather than fixed API quotas.
What ships with Aircall ⇄ TiDB

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Aircall and TiDB connectors work

Aircall

Integration surface
REST API (Aircall Public API v1, https://api.aircall.io/v1)
Authentication
HTTP Basic auth (base64 api_id:api_token) for single-account integrations, or OAuth 2.0 authorization_code flow for multi-tenant Technology Partner apps
Change detection
Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events; historical pulls via list endpoints paged with from/to timestamps and order
Capabilities
read · write · webhooks
Rate limits
60 requests per minute per company by default (120/min for Advanced Messaging customers); responses carry X-AircallApi-Limit, X-AircallApi-Remaining, and X-AircallApi-Reset headers
Aircall setup guide

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

    Choose tables

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

Aircall 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 333 integrations available for Aircall and TiDB.

Popular · 7 of 333
All Aircall 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