Skip to content
Back to Articles

Articles

How to connect Aircall to a CRM it doesn't support

Written by Roberto Postolovski, Founder & Tech LeadUpdated

When you need a custom integration

Aircall connects natively to many popular CRMs. You need your own integration when your CRM isn't one of them (an in-house system, an industry-specific CRM or a plain database), or when you need logic the native app doesn't run, like custom call outcomes or follow-up tasks.

We've built this before: Aircall call analytics (completed and missed calls, durations and outcomes) fed into a team's CRM workflow on a production B2B platform.

Pick the right events

Aircall's developer docs map webhook events to common jobs. Subscribe only to what you use:

  • call.ended: log or sync a complete call record
  • call.tagged and call.commented: sync tags and notes agents add
  • call.agent_declined and call.voicemail_left: handle missed calls and voicemails
  • call.created and call.answered: create live notes or tickets while the call is happening
  • call.comm_assets_generated: recording or voicemail links, when they aren't in call.ended yet

The integration, step by step

  1. 1.Receive

    Aircall sends each event as an HTTP POST to your endpoint. Reply with a success status immediately and process the event from a queue.

  2. 2.De-duplicate

    Aircall can deliver the same event more than once, so use the call ID as the key when writing. A repeated event updates the same record instead of creating a second one.

  3. 3.Match

    Look up the caller's number in your CRM. Normalise phone formats first, because the same number is often stored in several formats.

  4. 4.Write

    Create or update the call activity on the contact (or company, deal or ticket) with direction, duration, outcome, agent, tags and the recording link.

  5. 5.Follow up

    Missed calls and voicemails become callback tasks for the right person, so nothing depends on someone checking the Aircall app.

  6. 6.Handle the unmatched

    Calls from unknown numbers go to a review list instead of being dropped or attached to the wrong contact.

Limits to design around

  • The Public API is rate-limited to 120 requests per minute per API key or OAuth token, so use webhooks for day-to-day sync and the API only for backfills
  • Listing calls through the API returns at most 10,000 results per query: split historical imports into date windows
  • Aircall disables a webhook after 50 consecutive failed deliveries, so monitor your endpoint's health

What stays with your team

The conversation itself, decisions about deals and tickets, and calls that can't be matched to a record. The integration records what happened; people decide what it means.

Sources

Related

Have a process like this?

Tell us how it runs today. We'll tell you whether it can be automated, what it would take, and whether the numbers make sense.