Skip to content
Communications

Connect Aircall to any app with two-way sync.

Two-way sync Aircall across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • 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
Object catalog

What Stacksync syncs in Aircall.

These objects sync between Aircall and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Aircall exposes them.

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.
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.
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.
Numbers
Provisioned phone numbers with settings, open hours, and IVR config; read and update to keep routing and business-hours data aligned across systems.
Tags
Call tags with name and color; full CRUD, applied to calls for disposition and outcome reporting in the CRM or warehouse.
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.
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.
Webhooks
Event subscriptions for call, contact, user, message, and number events; full CRUD, the mechanism for near-real-time change delivery to Stacksync.
API surface

How Stacksync connects to Aircall.

The connector runs on Aircall's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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
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

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Supported
Aircall connector documentation
What ships with Aircall

Connect Aircall for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Aircall instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Aircall connector.

Aircall is the cloud phone and call-center system mid-market sales and support teams run their calling, SMS, and dialer on. IT and telecom admins own it, alongside RevOps and contact-center ops. Every call carries a recording, tags, comments, and metadata; contacts, users, teams, numbers, and SMS messages round out the system of engagement. That call and conversation data is the record sales, support, and compliance want joined to their CRM and warehouse.

  • RevOps
  • Sales operations
  • IT and telecom admins
  • Contact center operations
  1. 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.

  2. Two-way sync Contacts with CRM Contacts so reps' Aircall dialer lists match Salesforce or HubSpot and new CRM contacts appear in Aircall.

  3. Provision and deprovision Users and Team membership from an HR system or IdP so the agent roster, seats, and routing groups stay current.

  4. Send outbound SMS/MMS through the Messages API when a CRM or database record changes (appointment reminders, alerts) and write inbound replies back.

  5. Sync Tags and call dispositions onto matching CRM records as call outcomes so RevOps can report on conversation activity.

  6. Two-way sync Contacts between Aircall and a CRM so reps' click-to-dial lists always match Salesforce or HubSpot, and new CRM contacts appear in the Aircall dialer.

All Aircall integrations

Pick the system you need to keep in sync with Aircall. Each page covers the sync setup, field mapping, and common workflows for that pair.

How it works

Set up Aircall in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Aircall objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp

FAQ

Aircall connector FAQ

What can I sync with the Aircall connector?

Aircall's core objects — Contacts, Calls, Users, Numbers and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Aircall?

Via REST API (Aircall Public API v1, https://api.aircall.io/v1), authenticated with 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. Changes are detected as follows — webhooks (POST /v1/webhooks) for call, contact, user, message, and number events; historical pulls via list endpoints paged with from/to timestamps and order. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Aircall connector two-way?

Yes. Changes made in Aircall propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does an Aircall integration take to set up?

Most Aircall integrations go live in minutes: authenticate Aircall and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Aircall data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Aircall data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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.

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:

Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.