↑↓ selectEnter openEsc close

    1. Elbuz
    2. Connecting a PBX

    How to connect Aircall to Elbuz: API, Aircall user IDs instead of extensions, and Workspace

    5 min readUpdated

    Elbuz connects the Aircall API to the CRM: managers see the customer card while Aircall rings, dial from the card via Aircall Workspace; every call and its recording lands in the log and customer history.

    When you need this:

    • A customer calls — Elbuz pops up their name, city and recent orders.
    • A call was missed — “Pulse” gets a “Call back” task.
    • Need to call back — “Call” in the card sends the number to the manager's Workspace.
    • A supervisor wants to hear calls — recordings and voicemail play from the log, with an AI summary.

    Where to start: generate an API ID and token in Aircall Dashboard.

    What the Aircall integration does

    Through the , Elbuz starts calls in your Aircall Workspace, reconciles the call history every hour and fetches recording links. Through a , Aircall itself notifies Elbuz about every call. The main difference from other operators: Aircall has no extensions, so each employee in Elbuz gets their Aircall user .

    • Caller card. While Aircall is ringing, an “Incoming call” pop-up appears with the customer's name, city and orders (call card).
    • A missed call becomes a task. If the call was ringing a specific Aircall user, the manager gets a “Missed call” pop-up with a “Call back” button, and “Pulse” gets a high-priority task; it closes by itself after a conversation with that number.
    • Calls from the customer card. The number goes to the manager's desktop Workspace (how the call goes).
    • Recording, transcript and summary. The Aircall recording plays from the log, and AI analysis writes a summary to the customer's feed (AI call analysis).
    • All calls in one log. Incoming and outgoing calls of all managers, with the outcome, duration and wait time (call log).

    What you need from Aircall

    • An API ID and API token pair from Dashboard → Integrations → API keys.
    • A webhook to the Elbuz address — in the same Aircall account as the keys.
    • Aircall Workspace on the computer of every manager who calls from Elbuz: Elbuz can't start a call in the Aircall mobile app.
    • Customer phone numbers with the country code — Aircall won't accept a number without it (number format).

    Aircall Dashboard menu items are given in English, as in the Aircall interface. The paths come from the Aircall documentation; if an item is named differently, go by these pages or ask Aircall support:

    How to connect Aircall

    Three steps: API keys, the webhook and user IDs.

    Step one: API ID and API token

    1. Aircall Dashboard → Integrations → API keys.
    2. Click Generate API key (top right). Aircall shows a pair: API ID and API token.
    3. Copy both values right away: Aircall shows the token only once, and it's gone after you close the window. Lost it? Generate a new pair on the same page.

    Open the Aircall row in the “Telephony” group. The “Active” switch is already on — leave it that way. Fields:

    Form fieldWhat to enter
    “API ID”the API ID from Aircall
    “API token”the API token from the same pair
    “Line for outgoing calls”the Aircall number to call customers from (you can also enter the number's ID in Aircall). Leave it empty and Elbuz only fills in the customer's number in Workspace, while the manager picks the line
    Aircall connection card in the API access settings window
    1API ID and API token
    2Line for outgoing calls
    3Test connection
    1. API ID and API token — the keys from your Aircall account.
    2. Line for outgoing calls — the Aircall line number to call clients from.
    3. Test connection — checks the keys (do not press while capturing; shown for orientation).

    The form saves itself about a second after each edit: “Saving...” shows at the bottom, then “Saved”. Finally, click “Test connection”. Elbuz reads the list of Aircall users and changes nothing in your account:

    • the reply is “Connected to the PBX. Employees in the PBX: ‹count›”;
    • the “PBX extensions without an Elbuz employee” line lists the IDs and names of Aircall users not yet assigned to any employee;
    • the test reads only one page of the list (up to fifty users): in a large team, look up the remaining IDs in the Aircall Dashboard.

    Step two: the webhook in Aircall

    1. In the Elbuz form, copy the address from the “PBX webhook address” card with the “Copy” button.
    2. Aircall Dashboard → Integrations → Webhooks → Add webhook → Install Webhook.
    3. Name — any name; — the copied address. Leave Events alone: all of them are on by default, including the ones Elbuz needs.
    4. Click Add Webhook.
    PBX webhook address card with the key masked
    1Webhook address with masked key
    2Copy
    1. Webhook address — paste it into Aircall as a new webhook; the key at the end is masked here.
    2. Copy — copies the address to the clipboard.

    You don't need to enter the token that Aircall issues for the webhook in Elbuz. Every Aircall event carries this token, and Elbuz looks it up through the API by finding the webhook that points to the Elbuz address among yours. That's why the webhook must be created in the same Aircall account as the API ID and API token.

    After “Test connection”, Elbuz remembers the token in advance. If the webhook is recreated, Elbuz notices the new token on the very first event and rereads the list.

    Step three: Aircall user IDs in employee cards

    Aircall has no extensions: a call is tied to a user. So the “Internal phone” field of an Elbuz employee card gets that employee's Aircall user ID — a number. “Test connection” lists the IDs in the “PBX extensions without an Elbuz employee” line.

    From this ID, Elbuz knows who to show the incoming call card to, whose name to put in the “Manager” column of the log, and whose Workspace to call from when a manager clicks “Call”.

    To get Aircall working with Elbuz

    What reaches Elbuz

    FeatureHow it works with Aircall
    Calls from the card and log (“Call”)yes, through Aircall Workspace on the manager's computer (how the call goes)
    Incoming and outgoing calls in the logyes, from webhook events: right after the call ends, and finally when Aircall closes the call
    Incoming call card in Elbuz while ringingyes: when the call rings a specific Aircall user, the card goes to the Elbuz employee with that ID in “Internal phone”
    Call recording and voicemailyes: Elbuz requests the link from Aircall when you click “Play recording”
    Wait time separate from talk timeyes: Aircall sends when the call started, was answered and ended
    Hourly log reconciliationyes, at minute 25 of every hour, for the past 24 hours
    Customer name on the Aircall screenno: Aircall doesn't ask Elbuz who is calling
    Hang up from the incoming call cardno: the Aircall API has no such method, so the card has no “Hang up” button
    SMS through Aircallno
    Voice AI employeeno: Aircall isn't among the operators in the “Voice on the phone” section

    Aircall specifics

    How a call from the “Call” button goes

    Aircall only allows calls from Elbuz in Aircall Workspace on the computer — the mobile app won't work. At that moment the manager must be available and not on a call, otherwise Aircall replies “User not available” and Elbuz shows “The PBX rejected the request: HTTP 405: …”.

    • “Line for outgoing calls” is filled in — the manager's Workspace dials the customer from this line by itself. The manager must be assigned to this number in Aircall. If the account has no such number or ID, Elbuz replies “The PBX rejected the request: Aircall number not found: ‹number›”.
    • The field is empty — the customer's number appears in Workspace, and the manager picks the line and starts the call themselves.

    Aircall doesn't return a call ID in response to the request. Elbuz logs the attempt right away, and when a webhook event for the same number arrives, it adds the Aircall data to that row.

    Customer number format

    Aircall only accepts the customer's number in international format. Elbuz takes the digits from the card and puts “+” in front of them. A number saved as 067 123 45 67 turns into +0671234567, and Aircall rejects the call. Save customer phone numbers with the country code: +380 67 123 45 67.

    Which webhook events Elbuz uses

    Aircall eventWhat Elbuz does
    call.ringing_on_agentlooks up the customer by number, writes an “In progress” row and shows the “Incoming call” card to the employee with this ID in “Internal phone”. A call to a team (Team) without a specific user doesn't produce a card
    call.hunguplogs the call right away — the data is preliminary
    call.ended, call.voicemail_leftrefines the log row: outcome, duration, recording flag
    call.comm_assets_generatedmarks the recording or voicemail as ready

    Elbuz accepts and skips all other events.

    How an Aircall call becomes a result in the log
    What happened“Result” in the log
    answeredAnswered
    answered and transferred to someone elseTransferred
    a message was leftVoicemail
    the customer hung up right away, in the voice menu or in the queueCanceled
    the call hasn't ended yetIn progress
    anything elseNo answer

    Call recordings

    Aircall issues a recording link for one hour, so Elbuz doesn't store it but requests it every time you click “Play recording”. If there's no recording but there is voicemail, the voicemail plays.

    Hourly reconciliation

    Every hour, Elbuz fetches calls from Aircall for the past 24 hours and adds whatever events didn't bring. Aircall allows 120 API requests per minute for the whole company, so Elbuz pauses half a second between pages, and if the limit is hit anyway, it waits 10 seconds and continues. Your other Aircall integrations share the same limit.

    Scenarios

    All managers call from one company line

    Enter this line's number in “Line for outgoing calls” and assign all managers to it in Aircall. “Call” will dial the customer from the manager's Workspace right away, with nothing to choose.

    Managers have different lines

    Leave “Line for outgoing calls” empty. “Call” fills in the customer's number in Workspace, and the manager picks the line and starts the call.

    Incoming calls go to a team (Team)

    The incoming call card pops up for the manager whose phone rang as a specific user — that's why everyone has their Aircall user ID entered. While the call sits with the team without a specific user, there's no card; it still gets into the log — from the end event or the hourly reconciliation.

    What to do when Aircall won't call or calls don't come through

    What the app says and what to do about it
    What you seeWhyWhat to do
    “The PBX rejected the request: HTTP 405: …” The manager isn't in Aircall Workspace on the computer, isn't in “Available” status, or is already on a call Open Workspace on the computer, become available and click “Call” again
    “The PBX rejected the request: HTTP 400: …” The customer's number has no country code — after the “+” it became a nonexistent number Rewrite the phone number in the card as +380… (number format)
    “The PBX rejected the request: Aircall number not found: …” “Line for outgoing calls” contains a number or ID that doesn't exist in the Aircall account Enter the line number exactly as it appears in Aircall, or clear the field
    “Your employee card has no extension number” The “Internal phone” field is empty: Elbuz doesn't know whose Workspace to call from Enter the Aircall user ID (step three)
    Calls show up in the log only an hour later, and the incoming call card doesn't pop up The webhook wasn't created, has an old address, or was created in a different Aircall account than the API keys Copy the address from the “PBX webhook address” card again and check the webhook in Integrations → Webhooks of the same account
    The “Manager” column of the log shows a name from Aircall, not an Elbuz employee The employee card doesn't have their Aircall user ID, so the call isn't counted to them Take the ID from the “PBX extensions without an Elbuz employee” line and enter it in “Internal phone”

    Other cases where a call didn't show up are covered in the general troubleshooting of Telephony in Elbuz.

    FAQ

    Where do I get the API ID and API token in Aircall?

    Aircall Dashboard → Integrations → API keys → Generate API key. Aircall shows the API ID and API token; the token is visible only once, so copy it right away and enter it in the “API ID” and “API token” fields.

    What do I enter in “Internal phone” if Aircall has no extensions?

    The Aircall user ID — a number. The “Test connection” button lists the IDs in the “PBX extensions without an Elbuz employee” line. By this ID, Elbuz shows the incoming call card, labels the manager in the log and calls from their Workspace.

    Where in Aircall do I paste the address from Elbuz?

    Aircall Dashboard → Integrations → Webhooks → Add webhook → Install Webhook: in the URL field, paste the address from the “PBX webhook address” card, leave the events at their defaults, then click Add Webhook. You don't need to enter the webhook token in Elbuz.

    Why does “Call” return HTTP 405?

    Aircall starts a call only in Workspace on the computer, and only when the user is available and not on a call. Open Workspace, switch to “Available” status and try again.

    Can I listen to an Aircall call recording from Elbuz?

    Yes. “Play recording” asks Aircall for a fresh link every time, because Aircall issues it for one hour. If there's no recording but the customer left a voicemail, the voicemail plays.

    Can I call from Elbuz through the Aircall mobile app?

    No. Aircall starts a call from Elbuz only in Workspace on the computer.

    Can I hang up an Aircall call from Elbuz?

    No: the Aircall API has no such method, so the incoming call card has no “Hang up” button.

    Can I put a voice AI employee on an Aircall number?

    No: Aircall isn't among the operators in the “Voice on the phone” section. Supported operators are listed in Voice AI employee.

    Where to find it and who has access

    Menu
    Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → Aircall
    Aircall user ID
    “Users” → employee card → “Internal phone”
    Call log
    Directories → Contacts → Call log
    Access right
    system settings and the “Call log” window; you don't need any rights just to make calls
    Prepare
    access to the Aircall Dashboard; Aircall Workspace on the managers' computers

    The window that opens from the operator row is called “API access settings for external services”. Without the right to “Call log”, “Test connection” doesn't work, and neither does the webhook address. The general mechanics — log, call card, permissions — are in Telephony in Elbuz.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free