Two-way sync
Changes in Aircall or Intercom instantly reflect in both systems. No stale data, no manual imports.
Keep Aircall and Intercom in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Intercom 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 Segments, Admins & Teams, Articles, Contacts in Intercom with Teams, Messages (SMS/MMS), Webhooks, Contacts 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 Intercom. You decide which system owns which fields, and conflicts resolve by rules you set.
Activity handled in Aircall appears on the matching contact and account in Intercom, so the next person sees the full history without leaving the CRM.
Sends, bounces, opens, and replies from Aircall update fields on the contact in Intercom, so lead status reflects what actually reached the person.
A number, address, or unsubscribe recorded in either system updates the other, so no one calls a disconnected line or messages someone who opted out.
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 | Intercom objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Contacts A single contact model covers both users and leads, distinguished by a role attribute. | 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 applied to contacts, companies, and conversations sync for routing and reporting. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Custom Data Attributes Typed custom fields on contacts and companies hold synced billing and usage data. | Users is specific to Aircall and Custom Data Attributes to Intercom — 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. | Segments Saved audience definitions are readable for targeting parity across tools. | Numbers is specific to Aircall and Segments to Intercom — 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. | Admins & Teams Teammate records map conversation ownership to CRM users. | Teams is specific to Aircall and Admins & Teams to Intercom — 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. | Articles Help center content is accessible via API for knowledge sync and audits. | Messages (SMS/MMS) is specific to Aircall and Articles to Intercom — each maps to any object or custom field on the other side. |
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.
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 Intercom through its API, with automatic retries and rate-limit backoff.
DetectionIntercom notifies Stacksync of record changes through webhook events. Webhook topic subscriptions for contact, company, and conversation events, plus polling for backfill.
DeliveryEach detected change is written to Aircall through its API, with automatic retries and rate-limit backoff.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aircall–Intercom connection.
Changes in Aircall or Intercom instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Aircall or Intercom data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Aircall or Intercom record.
Track your Aircall ⇄ Intercom sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Aircall and Intercom.
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.
Authenticate Aircall and Intercom with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Aircall and Intercom 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Aircall and Intercom: authenticate both systems, choose the objects to sync (such as Aircall's Contacts and Tags), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Intercom: Calls, messages, and meetings on the record; Where Aircall sends at scale: delivery and reply status back on the contact; One contact list, opt-outs included. Activity handled in Aircall appears on the matching contact and account in Intercom, so the next person sees the full history without leaving the CRM.
Aircall: 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. Intercom: REST API. Authentication: OAuth 2.0 for public apps or a workspace access token. Stacksync manages authentication, retries, and rate limits on both sides.
Intercom: Conversations are composed of nested conversation parts (messages, notes, assignments), which matters when replicating full thread history. Aircall: Contacts support full CRUD plus search by phone number or email, making them the primary two-way object for keeping Aircall and a CRM in sync. Stacksync's field mapping accounts for these differences between Aircall and Intercom without custom code.
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means Aircall and Intercom records are not retained after a sync operation.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 417 integrations available for Aircall and Intercom.