Skip to content
Communications ⇄ Data warehouse

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

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

Land the messages, calls, and events from Aircall in ClickHouse as live tables, and write results back, without building or maintaining a pipeline.

Aircall produces a constant stream of activity — messages sent and received, calls placed and answered, meetings held, and the delivery and engagement events attached to them. That record is what the rest of the company wants to analyze, and it usually sits behind an API rather than in the warehouse. Building and babysitting an extraction pipeline is the tax most teams pay to get it out.

Stacksync syncs Tags, Teams, Messages (SMS/MMS), Webhooks from Aircall into tables in ClickHouse in real time, handling schema, rate limits, and retries. Because the connection works in both directions, results computed in ClickHouse — segments, contact updates, suppression flags — can be written back into fields in Aircall wherever it exposes them, so analysis lands where outreach actually happens.

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 Sync aggregated ClickHouse query results back into operational tools, such as account-level usage metrics into a CRM.
  • 04 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.

Common sync patterns

Activity joined with everything else

Combine Aircall's activity with the CRM, product, and support data already in ClickHouse to attribute outcomes to the touches that drove them, which no single tool can do alone.

Where Aircall accepts updates: operational write-back

Segments, contact fields, or suppression flags computed in ClickHouse sync back onto records in Aircall, putting warehouse analysis where the outreach happens.

Queryable history that outlives retention

A continuously synced copy in ClickHouse preserves messages, call logs, and events for reporting and audit even as they age out of Aircall or get purged inside it.

What you can sync between Aircall and ClickHouse

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 ClickHouse objects How this pairing syncs
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. Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Users is specific to Aircall and Dictionaries to ClickHouse — 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. Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Numbers is specific to Aircall and Tables (MergeTree family) to ClickHouse — 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 Namespaces that group tables and scope permissions for sync users. Tags is specific to Aircall and Databases to ClickHouse — each maps to any object or custom field on the other side.
Teams Groups of users for routing and reporting; create and delete teams and add or remove members to mirror org structure from an HR system or IdP. Views Saved queries used as curated, read-only sync sources. Teams is specific to Aircall and Views to ClickHouse — each maps to any object or custom field on the other side.
Messages (SMS/MMS) Text messages tied to a number and contact; send outbound SMS/MMS through the API and read inbound messages delivered via webhook events. Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Messages (SMS/MMS) is specific to Aircall and Materialized views to ClickHouse — each maps to any object or custom field on the other side.
Webhooks Event subscriptions for call, contact, user, message, and number events; full CRUD, the mechanism for near-real-time change delivery to Stacksync. Distributed tables Query-routing tables over cluster shards in self-managed deployments. Webhooks is specific to Aircall and Distributed tables to ClickHouse — each maps to any object or custom field on the other side.

How changes propagate between Aircall and ClickHouse

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 ClickHouse 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 ClickHouse as a row-level write, with types converted between the two schemas.

ClickHouse Aircall Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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.
What ships with Aircall ⇄ ClickHouse

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Aircall ⇄ ClickHouse 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 ClickHouse.

How the Aircall and ClickHouse 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

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write
How it works

How to connect Aircall to ClickHouse — 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 ClickHouse 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
    ClickHouse connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Aircall and ClickHouse 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 444 integrations available for Aircall and ClickHouse.

Popular · 8 of 444
All Aircall integrations All ClickHouse 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