Integrations · Automation

WebHook for call events and recordings

Q: Which events does ProZvonki send?

call_finished is sent after a call. You can also enable call_started, while recording_ready is sent as multipart when a call recording becomes available.

Q: Do I need my own server?

You need a reachable HTTPS URL. It can belong to your own server, n8n, Make or another service that accepts JSON and multipart/form-data POST requests.

Q: How is a call recording sent?

As a separate multipart/form-data request: JSON metadata is in the payload part and the binary audio file is in the recording part. Base64 is not used.

ProZvonki sends phone-call data to your HTTPS endpoint: direction, result, duration, number, SIM and, optionally, the contact name. A call recording arrives in a separate multipart request. Connect the Android dialer to n8n, Make, your CRM, a bot or your own server.

Set up the WebHook →

Connect any system

The WebHook is not tied to a specific CRM. The receiver can be an n8n or Make workflow, an internal system, a Telegram bot, analytics, a helpdesk or your own CRM API. You only need an HTTPS endpoint that accepts POST requests.

Call start and finish events

call_finished is sent after every eligible call. If you need real-time automation, enable the separate call_started event for incoming and outgoing calls. Both events share one stable call_id.

Clear call data

JSON includes a unique event_id, direction, result, who ended the call, the number or hidden-number flag, duration, UTC time, SIM slot and your manual SIM label. Sending the contact name is a separate opt-in.

Work SIM and custom labels

On a dual-SIM phone, send events only for the selected work SIM or for both SIMs. Each slot can have a custom label, such as a department, carrier or work number. It arrives in sim_label.

Call recordings without Base64

When call recording and “Send call recording” are enabled, ProZvonki sends a separate recording_ready event after the audio becomes available. The request uses multipart/form-data: JSON is in payload and the binary file is in recording.

Background delivery and retries

Events are delivered in the background. ProZvonki retries temporary network failures, timeouts and temporary server errors. Recording delivery survives app and device restarts. Repeated requests are possible, so the receiver should store event_id and avoid running the same action twice.

HTTPS and Bearer token

Use HTTPS. If your receiver requires authentication, enter a token and ProZvonki adds Authorization: Bearer <token>. The URL and token are stored in protected app settings. You can send a test event before the first real call.

FAQ

Frequently asked questions about the WebHook

Which events does ProZvonki send?

call_finished is sent after a call. You can also enable call_started, while recording_ready is sent as multipart after a call recording becomes available.

Do I need my own server?

You need a reachable HTTPS URL. It can be your own server, n8n, Make or another service that accepts JSON and multipart/form-data POST requests.

How is a call recording sent?

In a separate multipart request: JSON metadata is in the payload part and the binary audio file is in the recording part. Base64 is not used.

What happens when the device is offline?

The app keeps delivery jobs and retries temporary network and server failures. Your receiver must safely handle a repeated event_id.

How do I secure the WebHook?

Use HTTPS and, when needed, a Bearer token. The URL and token are stored securely on the device. Do not expose a secret in a public address or server log.

How is this different from Bitrix24 and amoCRM?

Bitrix24 and amoCRM integrations perform ready-made CRM actions such as cards, calls, deals and tasks. The WebHook sends universal events to your endpoint, where you implement the processing logic.