The 3CX CRM integration brings your PBX calls into the Elbuz CRM: managers call customers from the card with one button, and all calls land in the log and customer history automatically. Works with 3CX V20+.
When you need this:
- The manager doesn't know who is calling — 3CX shows the customer name from Elbuz on the phone and in the 3CX client.
- Numbers are dialed by hand — the “Call” button in the card: 3CX calls from the manager's extension.
- Missed calls get lost — a missed call becomes a “Call back” task in “Pulse”.
Where to start: create an API application in the 3CX console (how).
What Elbuz can do with 3CX
- Customer name on the phone — 3CX looks it up in Elbuz by number (name on the phone).
- Call from the customer card with one button — from the manager's extension (extensions).
- All calls in one log — whatever the template didn't deliver, the hourly reconciliation picks up (reconciliation).
- Incoming and missed call card — the customer's city, recent orders, a “Call back” task (call card).
- AI employee on the number — forwarding is set up by the 3CX administrator (voice AI).
What you need from 3CX
The Client ID and key are created in the 3CX admin console (per the 3CX documentation):
- 3CX Admin Console → “Integrations” → “API”.
- Click “Add” — a new client application is created.
- In “Client ID”, enter the number (DN) of the route point — it is also the ID used for authorization. The number must be free, not assigned to an employee.
- Select “3CX Call Control API Access”.
- Save: 3CX shows the API key only once — copy it right away.
Per the 3CX documentation, the Call Control requires an 8SC+ AI license. Without it, the “Call” button and the connection test with 3CX won't work.
3CX must be reachable from the internet at a public address. Elbuz doesn't connect to local network addresses: it checks the PBX address and rejects private ranges. If 3CX sits inside the office with no outside access, neither “Call” nor reconciliation will work.
The 3CX console paths are taken from the official documentation. If an item is named differently, use these pages or ask your 3CX provider:
How to connect 3CX to Elbuz
Three steps in order: keys, extensions and the XML template in the 3CX console. Without extensions the “Call” button doesn't work. Without the template the log is filled only by the hourly reconciliation, and the customer name doesn't appear on the phone.
Step one: 3CX keys
Open the 3CX row in the “Telephony” group. The “Active” toggle is already on — leave it that way. Fields to fill in:
| Form field | What to enter |
|---|---|
| “PBX address” | the public address of your 3CX, for example pbx.company.com, without https:// |
| “Client ID and Secret” | separated by a colon: 200:AbCdEf123 — the application ID and secret from the 3CX console |
1
Guide link2
Active switch3
PBX address field4
Client ID and Secret field5
Check connection button- The “Where exactly — step by step in the guide for your operator” link leads to this page.
- The “Active” switch — the integration is turned on.
- The “PBX address” field — the public address of your 3CX.
- The “Client ID and Secret” field — separated by a colon, for example 200:AbCdEf123.
- The “Check connection” button — a read-only request to the operator, changes nothing in the account.
The form saves itself about a second after each change: “Saving...” appears at the bottom, then “Saved”. There is no “Save” button.
Finally, click “Test connection”. Elbuz replies “Connected to the PBX. Employees in the PBX: ‹count›”. Elbuz gets an access token (valid for 60 minutes and renewed automatically) and reads the list of 3CX extensions with names. The line “PBX extensions without an Elbuz employee” shows who doesn't have a number in Elbuz yet.
Step two: extensions
When a manager clicks “Call”, 3CX first rings their extension and dials the customer only after they answer. The same number links calls in the log to the manager. In 3CX, this is the employee's extension number.
Where: employee card (“Users”) → the “Internal phone” field.
Below the connection form there is an “Employee extensions” card — a “Manager” / “Extension” table for all active employees. Rows with a dash are those who don't have a number yet.
Step three: XML template in the 3CX console
Instead of a webhook address, the form has a “PBX setup file” card with a “Download setup file” button. The file is a CRM integration XML template with the Elbuz address and secret key already filled in — you don't need to edit anything. Upload it to 3CX (per the 3CX documentation):
- 3CX Admin Console → “Integrations” → “CRM”.
- Click “Add Template” and select the downloaded file.
1
Download setup file button- The “Download setup file” button — a ready file with the address and key inside.
The file contains the Elbuz address with the secret key and the host you opened the form from. If you changed the domain or re-created the service in the list, download the file again and replace the template in 3CX.
To get 3CX working with Elbuz
What comes into Elbuz
Everything below was checked against the Elbuz 3CX integration module, built per the 3CX V20 Call Control API and XAPI documentation.
| Feature | How it works with 3CX |
|---|---|
| Calling from the card and the log (“Call”) | yes: 3CX calls from the manager's extension to the customer's number and waits 30 seconds for an answer |
| Incoming and outgoing calls in the log | yes, from the template report after the call ends and from the hourly reconciliation |
| Customer name on the phone screen | yes: 3CX looks up the name by number during the call and shows it on the phone and in the 3CX client |
| Incoming call card in Elbuz during the call | yes: 3CX passes the agent's extension in the name lookup (incoming call card) |
| Call recording | no: 3CX provides recordings only with separate authorization to its storage; no AI analysis either |
| Call outcome | only “Answered” or “No answer” (why) |
| Hourly log reconciliation | yes, at minute 25 of every hour, for the past 24 hours |
| Voice AI employee | set up by the PBX administrator (below) |
| Hang up from the incoming call card | no: for 3CX the incoming call card isn't linked to a log row, so it has no “Hang up” button |
The template has two scenarios:
- Contact lookup — during the call 3CX passes the number, direction and agent extension. Elbuz replies with the name, a link to the card and the same number (without it 3CX won't count a match).
- Call report — after the call 3CX passes the number, call type, agent extension and name, duration, start time and queue.
3CX specifics
Customer name on the phone
When the number is found among contacts, Elbuz returns the name, a link to the card and the number to 3CX. An unknown number gets an empty response — and 3CX shows just the number, not a nameless entry.
Incoming call card
Elbuz shows the “Incoming call” card to the manager whose extension is being called. 3CX passes this number in the name lookup as the agent extension — the current setup file does this.
If you connected 3CX earlier, your PBX has an old version of the template — its name lookup doesn't pass the agent extension, and the incoming call card doesn't pop up in Elbuz. Download the setup file again and replace the template in 3CX.
Call outcome
From the template report Elbuz knows the call type (incoming, outgoing, missed, no answer) and duration. A call with a duration that isn't marked as missed is “Answered”; all others are “No answer”. For 3CX you can't tell “Busy” from “Connection failure”, and wait time isn't passed separately.
Hourly reconciliation
Every hour Elbuz pulls the 3CX call log for the past 24 hours via XAPI. Field names have changed between V20 builds, so Elbuz looks for values under several known names.
If there's no call ID, Elbuz builds one from the time (to the minute), the customer number and the extension. The template report builds the key the same way, so one call doesn't end up as two rows; the exception is a call exactly at a minute boundary.
Voice AI employee on a 3CX number
An Elbuz AI employee can answer calls and call customers on its own. The conversation is handled not by your PBX but by the Elbuz voice platform, and the number has to be routed to it. The “Voice on the phone” section settings are covered in Voice AI employee.
3CX is your own PBX, so routing the number to AI is set up by its administrator. In the “Voice on the phone” section, enter the number, choose the “Other operator” operator and copy the address in the form <number>@<SIP-domain>.
The 3CX documentation doesn't describe whether or how your 3CX can route a number's calls to an external SIP address — check with your 3CX provider or integrator.
In “Operator addresses”, enter your 3CX public IP or domain — Elbuz will then accept SIP calls only from it. A domain is converted to an when the section is saved; if your 3CX IP changes, edit any field in the “Voice” section to save it again. Empty field — calls are accepted from any address.
For outgoing AI calls, the “Outgoing calls” block needs “SIP server”, “Line login” and “Line password” — the SIP account AI registers with as a phone. For “Other operator”, the SIP server is required. Where to get these for a 3CX extension and whether it can register from an external platform — ask your 3CX provider.
Outgoing calls work only when “Answer calls” is on: otherwise a test call replies “Outgoing calls are not set up: enter the line login and password and turn on answering calls”. By default AI calls from 9:00 to 20:00 account time — the “Call during hours” field.
Scenarios
The manager sees who is calling before answering
- Upload the current setup file to 3CX (step three).
- A customer calls — 3CX shows their name on the phone, and in Elbuz the “Incoming call” card pops up for the manager with that extension.
- After the call, the template report puts it into the log and the customer feed.
Update an old template
The incoming call card doesn't pop up, though the name shows on the phone — 3CX has a template uploaded before the update. Download the setup file from the form again and replace the template in “Integrations” → “CRM” with it (incoming call card).
A missed call doesn't get lost
The manager didn't pick up — a “Missed call” card pops up, and a “Call back” task appears in “Pulse”. In the log, “Missed only” filters these calls. More: missed calls.
What to do when 3CX doesn't work with Elbuz
General telephony problems — no call button, an empty log — are covered in Telephony in Elbuz. Here is what's specific to 3CX.
| What you see | Why | What to do |
|---|---|---|
| There's no “Call” button in the contact list or in the card | The keys aren't entered or the “Active” toggle is off — then call buttons aren't shown at all | Check the fields and the toggle in the connection form (step one) |
| “Your employee card has no extension number” | The “Internal phone” field in your card is empty: the PBX has nowhere to call in the first step | Enter the number in the employee card (step two) |
| “Test connection” returns an error even though the details are entered | Client ID and Secret aren't separated by a colon, the application has no Call Control API access, or the PBX address isn't reachable from the internet or points to a local network | Check the id:secret format, the application rights in the 3CX console and that the address is public |
| The phone doesn't show the customer name; calls appear in the log only once an hour | The CRM integration template isn't uploaded to 3CX or has an old address | Download the setup file again and replace the template in the 3CX console |
| An unknown number shows on the phone as a number, without a name | This is expected: for a number that isn't among contacts, Elbuz returns an empty response | Add the customer — next time 3CX will show the name |
| “The PBX did not answer in time. If the call did start, it will show up in the call log — check it before dialing again” | The operator didn't respond within 15 seconds. The request may have been accepted — then your phone will ring a bit later | Don't dial again right away: wait a minute. If the PBX accepted the request, your phone will ring, and after the call it will appear in the log |
FAQ
Which 3CX version is required for the Elbuz integration?
3CX V20 and later: Elbuz works through the Call Control API and XAPI of this version and the CRM integration XML template.
Where do I get the Client ID and Secret in 3CX?
3CX Admin Console → “Integrations” → “API” → “Add”: a free number as the Client ID and “3CX Call Control API Access” selected; 3CX shows the key once. An 8SC+ AI license is required (step by step).
Where do I upload the setup file from Elbuz?
In 3CX Admin Console: “Integrations” → “CRM” → “Add Template”. The Elbuz address and key are already in the file — nothing to fill in.
Can I listen to 3CX call recordings in Elbuz?
No. 3CX provides recordings only with separate authorization to its storage, so the log has no playback or AI analysis buttons for 3CX.
Does the integration work if 3CX is in the office?
Only if 3CX is reachable from the internet at a public address. Elbuz doesn't connect to local network addresses.
Can I route a 3CX number to the voice AI?
Your 3CX administrator sets this up: in the “Voice on the phone” section choose “Other operator” and copy the SIP address. Whether your 3CX can route a number to it — check with your 3CX provider or integrator.
Where it is and who has access
The 3CX connection lives among the other integrations, not in the call log. The window opened from the operator row is called “API access settings for external services”.
- Menu
- Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → 3CX
- Other entry points
- “Call log” → window menu → “Telephony connection”
- Access right
- system settings and the “Call log” window; no rights are needed to make calls
- Prepare
- the public address of 3CX (V20+), the Client and Secret, access to the 3CX console
Without the right to the “Call log”, “Test connection” and the setup file don't work.
Related topics
- For the overall picture of telephony and an operator comparison — Telephony in Elbuz.
- If the call is already in the log and you need to understand the columns or “Result” — Call log.
- If you want AI to answer and call customers on its own — Voice AI employee.
- If calls aren't linked to a manager — Users, the “Internal phone” field.
- If you need to find a conversation in the customer history — Contact card.
