Two-way sync
Changes in Aircall or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Keep Aircall and Salesforce in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
Salesforce 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 Custom Objects, Accounts, Contacts, Leads in Salesforce with Messages (SMS/MMS), Webhooks, Contacts, Calls 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 Salesforce. You decide which system owns which fields, and conflicts resolve by rules you set.
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.
A contact created or updated in Salesforce appears in Aircall within seconds, so outreach starts without exporting a list or re-keying numbers.
Names, phone numbers, email addresses, and the owning rep from Salesforce stay current in Aircall, so every call, text, or email goes to the right person at the right address.
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 | Salesforce 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 People linked to Accounts; synced two-way with marketing, support, and warehouse person records. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| Webhooks Event subscriptions for call, contact, user, message, and number events; full CRUD, the mechanism for near-real-time change delivery to Stacksync. | Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. | Webhooks is specific to Aircall and Products and Price Books to Salesforce — 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. | Custom Objects Org-specific tables with the __c suffix; discoverable via describe metadata so field mappings can be generated. | Calls is specific to Aircall and Custom Objects to Salesforce — 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. | Accounts Company records that anchor most syncs; typically mapped to customer tables in a database or ERP. | Users is specific to Aircall and Accounts to Salesforce — 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. | Leads Unqualified prospects; often written into Salesforce from enrichment or product-signup pipelines. | Numbers is specific to Aircall and Leads to Salesforce — 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. | Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. | Tags is specific to Aircall and Opportunities to Salesforce — 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 Salesforce through its API, with automatic retries and rate-limit backoff.
DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).
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–Salesforce connection.
Changes in Aircall or Salesforce instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Aircall or Salesforce 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 Salesforce record.
Track your Aircall ⇄ Salesforce sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Aircall and Salesforce.
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 Salesforce 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 Salesforce 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 Salesforce: authenticate both systems, choose the objects to sync (such as Aircall's Contacts and Webhooks), map fields visually, and changes propagate both ways in milliseconds — no code required.
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 Salesforce: Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting). Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Salesforce side: Custom Objects, Accounts, Contacts, Leads, plus custom fields where Salesforce exposes them. On the Aircall side: Messages (SMS/MMS), Webhooks, Contacts, Calls. 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 Salesforce: One contact list, opt-outs included; New contacts reachable right away; Where Aircall reaches out: contacts kept current. 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.
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. Salesforce: REST, SOAP, and Bulk APIs. Authentication: OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode. Stacksync manages authentication, retries, and rate limits on both sides.
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 441 integrations available for Aircall and Salesforce.