Real-time
Two-way sync
Changes in Aircall or Salesloft instantly reflect in both systems. No stale data, no manual imports.
Communications ⇄ CRM
Aircall to Salesloft integration — real-time, two-way sync
Keep Aircall and Salesloft 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 Salesloft
Keep Salesloft 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.
Salesloft 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 Fields, People, Accounts, Cadences in Salesloft with Users, Numbers, Tags, Teams 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 Salesloft. You decide which system owns which fields, and conflicts resolve by rules you set.
Common use cases
- 01 Reconcile ownership by syncing user assignments between the CRM and Salesloft.
- 02 Sync people, cadence memberships, and outcomes into a warehouse so RevOps can report on sequence performance next to pipeline data.
- 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
Where Aircall sends at scale: delivery and reply status back on the contact
Sends, bounces, opens, and replies from Aircall update fields on the contact in Salesloft, so lead status reflects what actually reached the person.
One contact list, opt-outs included
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.
New contacts reachable right away
A contact created or updated in Salesloft appears in Aircall within seconds, so outreach starts without exporting a list or re-keying numbers.
What you can sync between Aircall and Salesloft
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 | Salesloft objects | How this pairing syncs | |
|---|---|---|---|
| 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. | Calls Logged call activity with dispositions and recordings metadata. | 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. | Users Seller records used for ownership mapping and activity attribution. | Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. | |
| 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. | Cadences Multi-step outreach sequences that people are enrolled in and reported on. | Contacts is specific to Aircall and Cadences to Salesloft — 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. | Cadence Memberships Enrollment records linking a person to a cadence step and status. | Numbers is specific to Aircall and Cadence Memberships to Salesloft — 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. | Emails Sent and received email activity with engagement metadata, synced out for analytics. | Tags is specific to Aircall and Emails to Salesloft — 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. | Tasks Rep to-dos created and completed within cadences. | Teams is specific to Aircall and Tasks to Salesloft — each maps to any object or custom field on the other side. |
How changes propagate between Aircall and Salesloft
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 Salesloft 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 Salesloft through its API, with automatic retries and rate-limit backoff.
Salesloft Aircall Sub-second propagation
DetectionSalesloft notifies Stacksync of record changes through webhook events. Webhook event subscriptions plus polling on updated_at timestamps.
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.
- Salesloft: Subject to the platform's per-minute API rate limits.
What ships with Aircall ⇄ Salesloft
Connect Aircall and Salesloft for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aircall–Salesloft connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Aircall or Salesloft 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 Salesloft record.
Observability
Monitoring
Track your Aircall ⇄ Salesloft 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 Salesloft.
How the Aircall and Salesloft 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
Salesloft
- Integration surface
- REST API (v2)
- Authentication
- OAuth 2.0
- Change detection
- Webhook event subscriptions plus polling on updated_at timestamps
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's per-minute API rate limits
How it works
How to connect Aircall to Salesloft — 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 Salesloft 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
Salesloft
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Aircall and Salesloft 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 ⇄ SalesloftCustomers 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 SalesloftCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Aircall and Salesloft integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Aircall and Salesloft: authenticate both systems, choose the objects to sync (such as Aircall's Calls and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 Salesloft records are not retained after a sync operation.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Aircall and Salesloft connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Aircall–Salesloft integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Aircall and Salesloft. 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 Salesloft: Webhook event subscriptions plus polling on updated_at timestamps. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Salesloft side: Custom Fields, People, Accounts, Cadences, plus custom fields where Salesloft exposes them. On the Aircall side: Users, Numbers, Tags, Teams. Stacksync auto-detects both schemas and converts types between the two systems.
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 408 integrations available for Aircall and Salesloft.
Popular · 8 of 408
-
Aircall ⇄ Kommo -
Aircall ⇄ Kustomer -
Aircall ⇄ Nimble -
Aircall ⇄ Nutshell -
Salesloft ⇄ Gmail -
Salesloft ⇄ Amazon SES -
Salesloft ⇄ Infobip -
Salesloft ⇄ RingCentral
No integrations match .
