Skip to content
Communications ⇄ Database

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

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

Turn the messages, calls, and events Aircall handles into live rows in Citus, 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 Citus next to everything else.

Stacksync mirrors Users, Numbers, Tags, Teams from Aircall into Views, Sequences, Distributed tables, Reference tables in Citus 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 Provision and deprovision Users and Team membership from an HR system or IdP so the agent roster, seats, and routing groups stay current.
  • 02 Send outbound SMS/MMS through the Messages API when a CRM or database record changes (appointment reminders, alerts) and write inbound replies back.
  • 03 Sync high-volume event or tenant data from a Citus cluster into a warehouse for cross-tenant analytics.
  • 04 Write CRM or billing records into reference tables so distributed queries can join operational context locally on every node.

Common sync patterns

Trigger outbound communication from the database

Write a row to a synced table in Citus 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 Citus, so a phone number or email corrected on either side is current the next time either system uses it.

React to activity as it happens

Sends, replies, answered calls, or completed meetings arrive in Citus as row changes, so triggers, jobs, and services can respond in near real time.

What you can sync between Aircall and Citus

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 Citus 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. Sequences Key generators that matter when external writes must not collide with application inserts. Webhooks is specific to Aircall and Sequences to Citus — 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. Distributed tables Tables sharded across worker nodes by a distribution column; the main sync target for large datasets. Contacts is specific to Aircall and Distributed tables to Citus — 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. Reference tables Small lookup tables replicated to every node, synced like ordinary Postgres tables. Calls is specific to Aircall and Reference tables to Citus — 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. Local tables Coordinator-only tables that behave exactly like standard PostgreSQL tables. Users is specific to Aircall and Local tables to Citus — 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. Schemas Standard Postgres namespaces used to scope what a sync user can read and write. Numbers is specific to Aircall and Schemas to Citus — 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. Views Curated projections over distributed data, often used as read-only sync sources. Tags is specific to Aircall and Views to Citus — each maps to any object or custom field on the other side.

How changes propagate between Aircall and Citus

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

Citus Aircall Sub-second propagation

DetectionChanges in Citus are captured at the source via change data capture — no polling loop against its API. PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres.

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 ⇄ Citus

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Citus

Integration surface
PostgreSQL wire protocol; any standard Postgres driver connects to the coordinator node
Authentication
Database credentials (standard PostgreSQL authentication; managed deployments add cloud IAM options)
Change detection
PostgreSQL logical decoding / CDC, with caveats: changes to distributed tables occur on worker shards, so CDC setup differs from single-node Postgres
Capabilities
read · write · CDC
How it works

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

    Choose tables

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

Aircall and Citus 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 336 integrations available for Aircall and Citus.

Popular · 8 of 336
All Aircall integrations All Citus 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