Elbuz connects to UniTalk with a single API key: a manager calls a customer from the card in one click, and calls with recordings go to the call log and customer history automatically.
When you need this:
- The manager doesn't know who's calling — an incoming call card pops up on the Elbuz screen with the customer's name and recent orders.
- Numbers have to be dialed by hand — the “Call” button in the card: UniTalk connects the manager first, then the customer.
- Missed calls get lost — each one becomes a “Call back” task in “Pulse”.
Where to start: generate an API key in your UniTalk account (where exactly).
What Elbuz can do with UniTalk
- One-click call from the customer card — from the manager's extension (extensions).
- Call log and recordings — a permanent link to the recording is saved in the log (what reaches Elbuz).
- A clear call result — UniTalk call states are reduced to a few familiar ones (statuses).
- Incoming and missed call card — name, recent orders, a “Call back” task (call card).
- Call summary in the customer's history — AI analysis and the next step (AI call analysis).
What you need from UniTalk
You create the API key in your UniTalk account (according to the UniTalk knowledge base):
- UniTalk account → the “Integrations – API” section (Інтеграції – API).
- Click the button to create a key — it appears in a window; copy it.
UniTalk doesn't need a login, so the Elbuz form has a single field for the key. Employees' extensions (SIP lines) are listed in “Settings” → the “Users” tab.
The paths in the UniTalk account are taken from the operator's official documentation. If a menu item is named differently, use these pages or ask UniTalk support:
How to connect UniTalk to Elbuz
Three steps in order: the key, extensions and webhooks. Without extensions the “Call” button doesn't work. Without webhooks the log is filled only by the hourly reconciliation — with a delay of up to an hour.
Step one: UniTalk keys
Open the UniTalk row in the “Telephony” group. The “Active” switch is already on — leave it that way. In the “API key” field, enter the key from the “Integrations – API” section.
1
Link to the guide2
“Active” switch3
“API key” field4
“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 “API key” field — the key from the “Integrations – API” section.
- The “Check connection” button — a read-only request to the operator; it changes nothing in the account.
The form saves itself about a second after you edit it: you'll see “Saving...” at the bottom, then “Saved”. There is no “Save” button.
Finally, click “Test connection”. The UniTalk has no separate list of employees, so Elbuz checks the key by requesting the call log for the last hour. The reply is “Connected to the PBX. Employees in the PBX: 0”, without a “PBX extensions without an Elbuz employee” line. Elbuz treats an invalid key as a rejection, not as “no calls”.
Step two: extensions
When a manager clicks “Call”, UniTalk first rings their extension and dials the customer only after the manager answers. The same number links calls in the log to the manager.
Where: the employee card (“Users (employees)”) → the “Internal phone” field.
For UniTalk, enter the employee's extension (SIP line) from the UniTalk account in “Internal phone”. This is the number Elbuz passes to UniTalk as the “from” for the call. Elbuz treats only a short value, up to six digits, as an extension.
Below the connection form there is an “Employee extensions” card — a “Manager” / “Extension” table for all active employees. Rows with a dash are employees who don't have a number yet.
Step three: webhooks to the Elbuz address
The form has a “PBX webhook address” card with the address and a “Copy” button. You create the webhooks in UniTalk yourself (according to the UniTalk knowledge base):
- UniTalk account → “Integrations – API” → the “Add” button — the webhook form opens.
- “Action” — “Send webhook”, “Name” — for example “New call”, “URL” — the address from Elbuz, method — POST. No header with a key for Elbuz is needed: the secret inside the address itself verifies it.
- Request body — with the CALL_NEW event (which fields Elbuz reads). Save.
- Create a second webhook the same way — “Completed call” with the CALL_END event.
- Add both webhooks to the “Call event handling (Outgoing webhooks)” subsection of the “Integrations – API” section.
1
Address for the operator2
“Copy” button- The address you give to the operator; the secret key at the end is hidden in the frame.
- The “Copy” button — puts the address on the clipboard.
To get UniTalk working with Elbuz
What reaches Elbuz
Everything below is checked against the UniTalk integration module in Elbuz, written from the operator's API reference.
| Feature | How it works with UniTalk |
|---|---|
| Call from the card and the log (“Call”) | yes: a call from the manager's extension to the customer's number |
| Incoming and outgoing calls in the log | yes, from the CALL_END event; internal calls (INNER) aren't recorded |
| Incoming call card | yes, from the CALL_NEW, CALL_REDIRECT, CALL_ANSWER events if they contain an extension |
| Call recording | yes: a permanent link comes in the event; only for calls that took place |
| Hourly log reconciliation | yes, at minute 25 of every hour, covering the previous 24 hours |
| Customer name on the phone screen | no: UniTalk doesn't expect anything in response |
| Hang up a call from the incoming call card | yes: the “Hang up” button in the “Incoming call” card |
| Voice AI employee | not confirmed (below) |
From the webhook body, Elbuz reads the event field and the call object in the UniTalk event structure: id, direction, from, to, state, secondsTalk, secondsFullTime, link, date, outerNumber. The UniTalk knowledge base doesn't explain how to insert these fields into the request body template — check with UniTalk support if the form doesn't fill in the body itself.
UniTalk specifics
UniTalk request limits
UniTalk strictly limits request frequency: more than 30 in 10 seconds means a temporary block, more than 100 — a permanent one. That's why the hourly reconciliation pulls the log in the largest pages, 1000 calls each, pauses for a second between pages and stops at the twentieth.
Don't show the webhook address to outsiders
UniTalk events carry no signature, and the operator doesn't publish its server addresses, so the only protection is the secret key in the address.
Call recordings
UniTalk passes the recording link in an event field, and the link is permanent. It exists only for calls that took place: a missed or canceled call has no recording.
How statuses are read
UniTalk has more call states than other operators. Elbuz maps them like this:
| State in UniTalk | “Result” in the Elbuz call log |
|---|---|
| “No funds”, “external lines busy”, “number does not exist”, “unavailable”, routing error | “Connection failure” |
| blocked | “Canceled” |
| “busy” | “Busy” |
| no state received, there was a duration | “Answered” |
| no state received, no duration | “No answer” |
Customer number and comments
UniTalk passes the customer's number as digits only, without “+” or spaces — Elbuz strips them itself. Call comments from UniTalk aren't copied to the log: the comment field in the log belongs to the manager, and the reconciliation doesn't overwrite what they wrote.
Voice AI employee on a UniTalk 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, so the number has to be routed to it. Settings for the “Voice on the phone” section are in the Voice AI employee article.
Incoming calls: how to route the number to AI
In the “Operator” field of the “Voice on the phone” section, choose “Other operator”. In “Operator addresses”, enter, separated by commas, the addresses, subnets or domain of the PBX the operator will send calls to the SIP address from — operator support provides them. If the field is empty, Elbuz accepts calls to your SIP address from any address.
Elbuz converts a domain to IP addresses itself when the section is saved. If the PBX changes its IP, change any field in the “Voice” section so it is saved again.
The section shows an address like <number>@<SIP domain>. According to the UniTalk knowledge base, incoming call scenarios are set up in “Calls” → “Settings” → “Incoming scenarios” → “Add scenario”, and forwarding destinations include “external SIP account or other telephony”. Whether you can enter a number@domain address there — check with UniTalk support: the knowledge base doesn't say so directly.
Outgoing calls: a SIP line for AI calls
You get the line login and password in the UniTalk account (following UniTalk's instructions for softphones):
- “Settings” → the “Users” tab.
- Login — the extension; password — the “Show password” button.
- SIP server —
sip.unitalk.cloudor the one shown in the SIP line settings on the “Users” tab.
Enter them in “Line login”, “Line password” and “SIP server” in the “Outgoing calls” block. It's better to create a separate user for AI. Check with UniTalk support whether UniTalk allows calling customers from such a line via an external platform.
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
A manager calls a customer back from the card
- Enter the manager's UniTalk SIP line in “Internal phone” (step two).
- The manager clicks “Call” in the customer card — UniTalk rings the manager and, after they answer, dials the customer.
- After the conversation, the CALL_END webhook puts the call in the log with the recording and the result.
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”. Once a conversation with that number takes place, the task closes by itself. More: missed calls.
Find out why a call didn't go through
Filter the log by “Result” = “Connection failure”: it contains calls UniTalk didn't put through because of the balance, busy lines or a nonexistent number (how statuses are read).
What to do when UniTalk doesn't work with Elbuz
General telephony problems — no call button, an empty log, no recording — are covered in Telephony in Elbuz. Here is what's specific to UniTalk.
| 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” switch is off — call buttons aren't shown at all then | Check the fields and the switch 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 ring first | Enter the number in the employee card (step two) |
| “Test connection” returns an authorization error | The API key is invalid or deleted | Generate a key in “Integrations – API” again and re-enter it |
| Calls show up only once an hour | The webhooks weren't created, weren't added to call event handling, or the address has an old domain | Check the CALL_NEW and CALL_END webhooks in the UniTalk account and the address in them |
| UniTalk temporarily blocked the key | The limit of 30 requests in 10 seconds was exceeded — together with other integrations using the same key | Wait for the block to lift and don't use the same key in several integrations at once |
| “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 conversation the call will show up in the log |
FAQ
Where do I get a UniTalk API key for Elbuz?
In your UniTalk account, the “Integrations – API” section, the key generation button. Enter the key in the “API key” field of the UniTalk row in the “Telephony” group in Elbuz.
Which UniTalk webhooks does Elbuz need?
Two outgoing POST webhooks to the address from the “PBX webhook address” card: one for a new call (CALL_NEW) and one for a completed call (CALL_END). Add them to call event handling in the “Integrations – API” section.
Can Elbuz get my UniTalk key blocked with frequent requests?
Elbuz respects UniTalk limits: the reconciliation pulls the log in pages of 1000 calls with a pause between them. A risk appears if other integrations use the same key at the same time.
Why does the check show “Employees in the PBX: 0”?
The UniTalk API has no separate list of employees, so Elbuz checks the key by requesting the call log for the last hour. Zero is a normal reply for UniTalk.
Will UniTalk show the customer's name on the manager's phone?
No: UniTalk doesn't expect a reply with a name from the . The manager sees who's calling in the incoming call card on the Elbuz screen (call card).
Can I choose the number UniTalk uses to call the customer?
No. The UniTalk call API doesn't accept a line number, so the UniTalk form has no “Line for outgoing calls” field.
Can I route a UniTalk number to the voice AI?
There are no ready-made instructions. Check with UniTalk support whether the number can be forwarded to the external SIP address from the “Voice on the phone” section (what's known so far).
Where to find it and who has access
The UniTalk connection sits with the other integrations, not in the call log. The window that opens from the operator row is called “API access settings for external services”.
- Menu
- Account → System settings → “Other settings” → “External services and integrations” → “Telephony” → UniTalk
- Other ways in
- “Call log” → window menu → “Telephony connection”
- Access right
- system settings and the “Call log” window; you don't need any rights just to make calls
- Prepare
- the UniTalk API key, employees' extensions ( lines)
Without the right to “Call log”, “Test connection”, the webhook address and the settings file don't work.
Related topics
- If you need the overall picture of telephony and a comparison of operators — 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's history — Contact card.
