Skip to content
Communications ⇄ CRM

Aircall to Clari integration — real-time, two-way sync

Keep Aircall and Clari 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 Clari

Keep Clari 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.

Clari 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 Account field extensions, Opportunity field extensions, Audit Events, Forecast in Clari 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 Clari. You decide which system owns which fields, and conflicts resolve by rules you set.

Common use cases

  • 01 Enrich Clari Account records with firmographic or billing data points through the ingest API in incremental mode.
  • 02 Stream Audit Events into a reporting database to monitor forecast-submission changes and user activity for compliance.
  • 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 Clari 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 Clari 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 Clari, so the next person sees the full history without leaving the CRM.

What you can sync between Aircall and Clari

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 Clari objects How this pairing syncs
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. Account field extensions External data points written onto Account records through the ingest API in initial or incremental mode; requires an apikey plus a partnerkey. Messages (SMS/MMS) is specific to Aircall and Account field extensions to Clari — 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. Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Webhooks is specific to Aircall and Opportunity field extensions to Clari — each maps to any object or custom field on the other side.
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. Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. Contacts is specific to Aircall and Audit Events to Clari — 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. Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Calls is specific to Aircall and Forecast to Clari — 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. Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Users is specific to Aircall and Quota to Clari — 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. Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. Numbers is specific to Aircall and Opportunities to Clari — each maps to any object or custom field on the other side.

How changes propagate between Aircall and Clari

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

Clari Aircall Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

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.
  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
What ships with Aircall ⇄ Clari

Connect Aircall and Clari for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Aircall–Clari connection.

Real-time

Two-way sync

Changes in Aircall or Clari instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Aircall or Clari 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 Clari record.

Observability

Monitoring

Track your Aircall ⇄ Clari 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 Clari.

How the Aircall and Clari 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

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
How it works

How to connect Aircall to Clari — 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 Clari 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
    Clari connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Aircall and Clari 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 ⇄ Clari
    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 Clari
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Aircall and Clari 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 326 integrations available for Aircall and Clari.

Popular · 8 of 326
All Aircall integrations All Clari 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