Aircall → Attio: the calls find the right record

Most teams using Aircall have a folder of call recordings and a CRM full of blank call-activity fields. The native integrations work for the basics but fall over on custom objects, call dispositions, or linking to the right deal. We wire Aircall into Attio with the exact object model you designed - calls land on the right Person and the right Company, disposition and outcome are structured fields, recordings and transcripts are accessible without leaving Attio.

Direction

Aircall → Attio (calls, recordings, voicemails)

Stack

Aircall API, Attio API, n8n

The what

What this integration actually does

Every inbound and outbound call creates an activity on the matching Attio Person - matched by phone number with fallback rules. Duration, outcome, disposition tag, agent, and recording link are captured as structured fields. Missed calls and voicemails get their own activity type so pipeline views can filter them.

The how

How we build it

1
Map Aircall disposition tags to Attio activity outcomes - "left voicemail", "connected", "meeting booked", etc.
2
Register Aircall webhooks on call.created, call.ended, call.tagged.
3
Match the phone number to an Attio Person with fallback to Company main line, then to a new record flagged for review.
4
Write the activity with duration, outcome, agent, and recording URL.
5
Optional: transcription via Aircall's built-in or a separate service (Fathom, Gong) for high-value calls.
6
Dashboard: calls-per-deal, connect rate by agent, disposition breakdown - inside Attio.

Under the hood

What lives inside the pipeline

Phone number normalization (E.164) before matching - avoids false negatives on differently-formatted numbers.
Voicemail detection - missed calls and VMs separated from connected calls.
Agent-to-Attio-user mapping so activity ownership is right.
Recording link stored as URL, not downloaded - saves storage and respects compliance.
Optional AI summary of long calls (opt-in per call).

Hard-earned lessons

What we learned the hard way

The native Aircall integration writes to Contact objects with a rigid schema. For custom objects, go via the API.
Inbound calls from unknown numbers should create a placeholder Person, not be discarded - that's often a new lead.
Recording URLs expire in Aircall. If you need permanent archive, copy to your own storage - but then mind the compliance implications.
Disposition tagging discipline is everything. Without it, the reports are meaningless. Enforce required dispositions.

Case study

Inside-sales team, 200 calls/day

Problem

Calls logged in Aircall, CRM activity showed "call" with no outcome, no recording, no context. Pipeline reviews turned into hunt-the-recording sessions.

Solution

Full webhook sync with dispositions, recordings, and agent mapping. Dashboards inside Attio for connect rate, calls per deal, and disposition mix.

Outcome

Pipeline reviews got 10x faster because every call had context. Dispositions became a real coaching signal, not an afterthought.

FAQ

Questions we get

Same pattern works. Aircall is our reference because it has the cleanest webhook payload. Allo is AI-first - see the Allo integration for that flavor. Kixie and Dialpad need a touch more normalization.

Yes - click-to-call via the Aircall browser extension or an Attio action that opens the Aircall dialer.

Aircall handles consent at the call level. The integration respects whatever Aircall's configured to do.