Skip to content

Phone to CRM integration for Ringover and Aircall

Calls happen in Ringover or Aircall; clients and deals live in Zoho CRM, HubSpot or Pipedrive. In between, someone types up call notes at the end of the day, when they remember. We connect the two with n8n: each call lands on the right record, an unknown number becomes a lead, a missed call becomes a task.

01What the integration does

  • Every call on the right contact: direction, duration, outcome and the person who took it, written to the CRM when the call ends.
  • Unknown numbers become leads: a number the CRM has never seen creates a lead with the source “inbound call”, an owner picked by your rule (round-robin across the salespeople you list, or by region) and a task to qualify it.
  • Missed-call alerts: a missed call creates a callback task for the contact’s owner, and callbacks still open show on the dashboard.
  • Recordings and summaries linked: when your phone plan records calls, the link to the recording, and the transcript or summary if your phone system produces one, sits on the call in the CRM.

02Where the native integration stops and ours takes over

Ringover and Aircall both ship native CRM integrations, and for many teams they are enough. Here is what their own documentation says, checked on 17 October 2026.

  • Ringover allows one active integration per category at a time, so one CRM. Its HubSpot integration needs a Business or Advanced Ringover account, recordings have to be switched on in Ringover first, and a conversation history on customer profiles needs the Omnichannel add-on.
  • Aircall’s HubSpot integration needs every phone number in HubSpot saved in E.164 format (+33…). When two contacts share a number, the call goes to the record updated most recently. A contact is created for an unknown number only if your Aircall settings allow it.
  • Both publish webhooks for call events, which is what an n8n flow listens to.

03What n8n adds on top

  • Your matching rule instead of “most recently updated”: for example, the contact with an open deal wins, and real ties go to a review list.
  • Clean numbers on both sides: existing CRM numbers are converted to international format once, and every incoming number before the lookup, so 06 11 22 33 44 and +33 6 11 22 33 44 are the same person.
  • More than one destination: the same call can update the CRM, the KPI dashboard and a second tool, which a one-CRM native integration cannot do.
  • Your call history: past calls still available through the phone system’s API can be imported with the same rules, so the CRM starts complete.

04Three call flows, written out

Generic examples with made-up numbers. The same flows run with Ringover or Aircall.

Exhibit 1Inbound call from a number the CRM does not know
Trigger
A call from +33 6 00 00 00 01 ends.
Steps
  1. 1.The phone system sends the call-ended event to n8n.
  2. 2.n8n converts the number to international format and searches the CRM. No contact matches.
  3. 3.It creates a lead named after the number, marked “inbound call, to qualify”, and assigns it to the next salesperson in the rotation.
  4. 4.The call is attached to the lead with its duration and recording link.
Result
A second call from the same number lands on this lead instead of creating another one.
Exhibit 2Missed call to callback
Trigger
A client calls the sales line at 12:40 and nobody answers.
Steps
  1. 1.n8n finds the client’s contact and its owner.
  2. 2.It creates a callback task for that owner, due before the end of the day.
  3. 3.If the task is still open at 17:00, the sales lead gets a message. The deadline and the escalation time are settings agreed during the review.
Result
Every missed call ends as a task with an owner and a due time, and the dashboard counts the ones still open.
Exhibit 3Call ended to activity on the open deal
Trigger
A salesperson finishes a 14-minute call with an existing client.
Steps
  1. 1.n8n matches the number to the contact and looks for an open deal.
  2. 2.The call is logged on the contact and on the deal, with the outcome the salesperson picked.
  3. 3.The summary, if the phone system produced one, is added as a note on the deal.
Result
The deal’s timeline shows the call with its duration, outcome and summary note, so whoever picks the deal up next can read it before calling.

05How a project runs

  1. 01

    Review

    A free 30-minute call. You show us the tools you use and the step that costs your team the most time.

  2. 02

    Written quote in 48 hours

    Scope, flows, what is left out, timeline and one price. The price is fixed once you sign.

  3. 03

    Build in your accounts

    The workflows run in your n8n and your CRM, under your logins. If we stop working together, everything stays with you.

  4. 04

    Runbook

    Each flow comes with a short document: what starts it, what it changes, and what to check when it stops.

  5. 05

    Care plan

    Monthly monitoring, fixes and small changes. A failed run alerts us, so your team does not have to watch for it.

06Questions buyers ask

We already use the native integration. Why add n8n?

Keep it if it covers what you need. Teams usually call us for the gaps: a matching rule of their own, unknown callers handled as leads, missed calls turned into tasks, or call data that has to reach more than one tool. n8n can run next to the native integration or replace it; we say which after the review.

Does it work with Zoho CRM, HubSpot and Pipedrive?

Yes. n8n has built-in nodes for all three, and the phone side goes through Ringover’s or Aircall’s webhooks and API. A CRM without a node, including a custom one, works through its API.

Do you need access to our call recordings?

No. The flow stores the link to the recording on the CRM record; the audio stays in your phone system, under its access rules. We only need an API key with the permissions the flow uses.

What about calls made before the integration?

Past calls that the phone system’s API still returns can be imported with the same matching rules, then kept in sync. For a sales team of six, we imported its existing Ringover history this way; more than 183,000 calls are synced today (case study below).

What if Ringover or Aircall changes something?

Under a care plan, we watch for failed runs and fix them within the plan’s response time. Changes on the vendor side are the most common cause of a break, which is why each flow has a runbook.

07Related work

Show us the tool that costs you the most time.

A 30-minute call, then a written quote within 48 hours. Fixed once signed. VAT not applicable, art. 293 B of the French CGI.