Skip to content
Communications ⇄ CRM

Aircall to Microsoft Dynamics 365 Sales integration — real-time, two-way sync

Keep Aircall and Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales

Keep Microsoft Dynamics 365 Sales 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.

Microsoft Dynamics 365 Sales 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 Opportunities, Quotes, Orders, Invoices in Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales. You decide which system owns which fields, and conflicts resolve by rules you set.

Common use cases

  • 01 Run a two-way dual-run between Dynamics and another CRM during a migration.
  • 02 Feed BI models with continuously updated CRM data instead of scheduled exports.
  • 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 Microsoft Dynamics 365 Sales, 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 Microsoft Dynamics 365 Sales appears in Aircall within seconds, so outreach starts without exporting a list or re-keying numbers.

What you can sync between Aircall and Microsoft Dynamics 365 Sales

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 Microsoft Dynamics 365 Sales 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 Person records linked to accounts; synced with marketing and support systems. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
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. Opportunities Deal records with stages and estimated revenue; synced for pipeline reporting and close-triggered workflows. Messages (SMS/MMS) is specific to Aircall and Opportunities to Microsoft Dynamics 365 Sales — 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. Quotes Pricing proposals; often synced with CPQ or ERP pricing data. Webhooks is specific to Aircall and Quotes to Microsoft Dynamics 365 Sales — 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. Orders Confirmed sales; handed off to ERP systems for fulfillment and billing. Calls is specific to Aircall and Orders to Microsoft Dynamics 365 Sales — 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. Invoices Billing records; usually mastered in the ERP and mirrored back for seller visibility. Users is specific to Aircall and Invoices to Microsoft Dynamics 365 Sales — 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. Activities Emails, calls, appointments, and tasks; read out for activity analytics. Numbers is specific to Aircall and Activities to Microsoft Dynamics 365 Sales — each maps to any object or custom field on the other side.

How changes propagate between Aircall and Microsoft Dynamics 365 Sales

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 Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales through its API, with automatic retries and rate-limit backoff.

Microsoft Dynamics 365 Sales Aircall Sub-second propagation

DetectionMicrosoft Dynamics 365 Sales notifies Stacksync of record changes through webhook events. Dataverse change tracking with delta tokens, plus registered webhooks on table events.

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.
  • Microsoft Dynamics 365 Sales: Requests are governed by Dataverse service protection limits evaluated per user and time window.
What ships with Aircall ⇄ Microsoft Dynamics 365 Sales

Connect Aircall and Microsoft Dynamics 365 Sales for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aircall–Microsoft Dynamics 365 Sales connection.

Real-time

Two-way sync

Changes in Aircall or Microsoft Dynamics 365 Sales instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Aircall or Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales record.

Observability

Monitoring

Track your Aircall ⇄ Microsoft Dynamics 365 Sales 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 Microsoft Dynamics 365 Sales.

How the Aircall and Microsoft Dynamics 365 Sales 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
Aircall setup guide

Microsoft Dynamics 365 Sales

Integration surface
Dataverse Web API (OData v4 REST)
Authentication
OAuth 2.0 via Microsoft Entra ID
Change detection
Dataverse change tracking with delta tokens, plus registered webhooks on table events
Capabilities
read · write · webhooks
Rate limits
Requests are governed by Dataverse service protection limits evaluated per user and time window.
How it works

How to connect Aircall to Microsoft Dynamics 365 Sales — 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.

  1. 01

    Connect your apps

    Authenticate Aircall and Microsoft Dynamics 365 Sales with each platform's 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
    Microsoft Dynamics 365 Sales connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Aircall and Microsoft Dynamics 365 Sales 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.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Aircall ⇄ Microsoft Dynamics 365 Sales
    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 Microsoft Dynamics 365 Sales
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Aircall and Microsoft Dynamics 365 Sales integration FAQ

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.

Learn more about security
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:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 335 integrations available for Aircall and Microsoft Dynamics 365 Sales.

Popular · 8 of 335
All Aircall integrations All Microsoft Dynamics 365 Sales integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

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

Book a demo Tour the platform on your own