Real-time
Two-way sync
Changes in Aircall or Kustomer instantly reflect in both systems. No stale data, no manual imports.
Communications ⇄ CRM
Aircall to Kustomer integration — real-time, two-way sync
Keep Aircall and Kustomer 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 Kustomer
Keep Kustomer and Aircall working from the same contacts, and log every call, message, and meeting back on the record, in real time and in both directions.
Kustomer holds the people the business talks to: the contacts, their phone numbers and email addresses, and which rep owns the relationship. Aircall is where the talking happens, whether that is calls, texts, email, or meetings. The two depend on the same people, and when the contact list in one drifts from the other, outreach goes to stale numbers and the record of what was said never makes it back to the account.
Stacksync syncs Notes, Customers, Conversations, Messages in Kustomer with Contacts, Calls, Users, Numbers in Aircall field by field, in real time, and in both directions. Current contact details flow out to Aircall so it can reach the right person, and the calls, messages, and meetings Aircall produces flow back onto the matching record in Kustomer. You decide which system owns which fields, and conflicts resolve by rules you set.
Common use cases
- 01 Escalate conversation-derived signals into the CRM as tasks or opportunities
- 02 Sync customers bi-directionally with the CRM and ERP so agents see deal, billing, and subscription context on the timeline
- 03 Provision and deprovision Users and Team membership from an HR system or IdP so the agent roster, seats, and routing groups stay current.
- 04 Send outbound SMS/MMS through the Messages API when a CRM or database record changes (appointment reminders, alerts) and write inbound replies back.
Common sync patterns
New contacts reachable right away
A contact created or updated in Kustomer appears in Aircall within seconds, so outreach starts without exporting a list or re-keying numbers.
Where Aircall reaches out: contacts kept current
Names, phone numbers, email addresses, and the owning rep from Kustomer stay current in Aircall, so every call, text, or email goes to the right person at the right address.
Calls, messages, and meetings on the record
Activity handled in Aircall appears on the matching contact and account in Kustomer, so the next person sees the full history without leaving the CRM.
What you can sync between Aircall and Kustomer
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 | Kustomer 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. | Users Agent records map conversation ownership to people in other systems. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Tags Call tags with name and color; full CRUD, applied to calls for disposition and outcome reporting in the CRM or warehouse. | Tags Labels on conversations and customers sync for categorization and analytics. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping. | |
| 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. | Teams Team assignments support routing parity and reporting. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Numbers Provisioned phone numbers with settings, open hours, and IVR config; read and update to keep routing and business-hours data aligned across systems. | Conversations Support threads across channels sync outward for analytics and CRM context. | Numbers is specific to Aircall and Conversations to Kustomer — 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. | Messages Individual messages within conversations support full-thread replication. | Messages (SMS/MMS) is specific to Aircall and Messages to Kustomer — 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. | Companies Organization records group customers and map to CRM accounts. | Webhooks is specific to Aircall and Companies to Kustomer — each maps to any object or custom field on the other side. |
How changes propagate between Aircall and Kustomer
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 Kustomer 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 written to Kustomer through its API, with automatic retries and rate-limit backoff.
Kustomer Aircall Sub-second propagation
DetectionKustomer notifies Stacksync of record changes through webhook events. Outbound webhooks on record events, plus polling for backfill.
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.
- Kustomer: Subject to the platform's API rate limits.
What ships with Aircall ⇄ Kustomer
Connect Aircall and Kustomer for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aircall–Kustomer connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Aircall or Kustomer 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 Kustomer record.
Observability
Monitoring
Track your Aircall ⇄ Kustomer 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 Kustomer.
How the Aircall and Kustomer 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
Kustomer
- Integration surface
- REST API
- Authentication
- API key used as a bearer token, scoped by role
- Change detection
- Outbound webhooks on record events, plus polling for backfill
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Aircall to Kustomer — 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.
- 01
Connect your apps
Authenticate Aircall and Kustomer with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Aircall
connected
Kustomer
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Aircall and Kustomer 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.
objects · Aircall ⇄ KustomerCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Aircall KustomerCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Aircall and Kustomer integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Aircall and Kustomer: authenticate both systems, choose the objects to sync (such as Aircall's Users and Tags), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Yes — Stacksync ships production-grade connectors for both Aircall and Kustomer. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Aircall: Webhooks (POST /v1/webhooks) for call, contact, user, message, and number events; historical pulls via list endpoints paged with from/to timestamps and order. On Kustomer: Outbound webhooks on record events, plus polling for backfill. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Kustomer side: Notes, Customers, Conversations, Messages, plus custom fields where Kustomer exposes them. On the Aircall side: Contacts, Calls, Users, Numbers. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Aircall and Kustomer: New contacts reachable right away; Where Aircall reaches out: contacts kept current; Calls, messages, and meetings on the record. A contact created or updated in Kustomer appears in Aircall within seconds, so outreach starts without exporting a list or re-keying numbers.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 322 integrations available for Aircall and Kustomer.
Popular · 7 of 322
-
Aircall ⇄ Close -
Aircall ⇄ Copper CRM -
Aircall ⇄ Creatio CRM -
Kustomer ⇄ RingCentral -
Kustomer ⇄ Zoom -
Kustomer ⇄ Gmail -
Kustomer ⇄ Amazon SES
No integrations match .
