Skip to content
Communications ⇄ Data warehouse

Aircall to Apache Druid integration — real-time, two-way sync

Keep Aircall and Apache Druid 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 Apache Druid

Land the messages, calls, and events from Aircall in Apache Druid 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 Calls, Users, Numbers, Tags from Aircall into tables in Apache Druid in real time, handling schema, rate limits, and retries. Because the connection works in both directions, results computed in Apache Druid — 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 Log every Call with its recording URL, tags, comments, and metadata into Postgres or a warehouse for talk-time and call-outcome reporting beside CRM pipeline data.
  • 02 Provision and deprovision Users and Team membership from an HR system or IdP so the agent roster, seats, and routing groups stay current.
  • 03 Expose product telemetry stored in Druid to business tools without granting direct cluster access.
  • 04 Query aggregated event metrics from Druid and sync them into CRM account fields for usage-based selling.

Common sync patterns

Engagement and delivery on live data

Sends, opens, clicks, bounces, and call outcomes from Aircall land in Apache Druid as they happen, so deliverability and response monitoring stop lagging the reality they describe.

Activity joined with everything else

Combine Aircall's activity with the CRM, product, and support data already in Apache Druid 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 Apache Druid sync back onto records in Aircall, putting warehouse analysis where the outreach happens.

What you can sync between Aircall and Apache Druid

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 Apache Druid objects How this pairing syncs
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. Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. Calls is specific to Aircall and Ingestion Supervisors to Apache Druid — 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. Lookups Key-value mappings joined at query time, refreshable from external systems. Users is specific to Aircall and Lookups to Apache Druid — 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. Tasks Batch ingestion and compaction jobs monitored during data loads. Numbers is specific to Aircall and Tasks to Apache Druid — 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. Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Tags is specific to Aircall and Datasources to Apache Druid — 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. Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Teams is specific to Aircall and Segments to Apache Druid — 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. Dimensions String and categorical columns used for filtering and grouping in synced queries. Messages (SMS/MMS) is specific to Aircall and Dimensions to Apache Druid — each maps to any object or custom field on the other side.

How changes propagate between Aircall and Apache Druid

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

Apache Druid Aircall Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

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.
  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
What ships with Aircall ⇄ Apache Druid

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity
How it works

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

    Choose tables

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

Aircall and Apache Druid 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 344 integrations available for Aircall and Apache Druid.

Popular · 8 of 344
All Aircall integrations All Apache Druid 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