Bitrix24 Integration
Two-way sync of your Bitrix24 CRM with Astervis.
Connect Bitrix24 and your calls stop living in a separate world from your CRM. Astervis mirrors your org chart, pipelines and records into its own store, links every call to the right deal and contact, and keeps both sides current as things change in Bitrix24. The sales dashboards you'll use day to day are driven by this synced data — no separate report to maintain.
Everything runs on your own server. The webhooks travel directly between your Bitrix24 account and your Astervis instance; your call recordings never leave the box.
What syncs
Astervis pulls a fairly complete slice of your Bitrix24 CRM, in a sensible order so that relationships resolve correctly — the org structure first, then the pipeline definitions, then the records that hang off them.
| What | Why it matters |
|---|---|
| Departments | Your Bitrix24 org structure, so calls and operators map onto real teams. |
| Employees | Staff and their extensions — this is how a call's operator resolves to a named person. |
| Categories | Deal pipelines (Bitrix24 calls them categories). Each category is its own funnel. |
| Pipeline stages | The statuses inside each category, in order — the backbone of your funnel charts. |
| Leads | Early, unqualified opportunities, with their source and status. |
| Deals | The records that power the sales dashboards — value, stage, owner, linked contact/company. |
| Deal-stage history | Every stage transition a deal has been through, so you can measure how the funnel actually moves over time. |
| Contacts | People — names, all phone numbers, emails. Phone numbers are what call matching keys off. |
| Companies | Organizations, linked to their contacts and deals. |
This is a read sync: Bitrix24 is the source of truth and Astervis mirrors it. Astervis
doesn't write deals or contacts back into Bitrix24 — it reads your CRM so it can attach
calls to records and drive analytics. Need extra fields beyond the standard ones? See
Custom fields for syncing your UF_ user fields.
Setup
You'll connect Astervis to Bitrix24 with an inbound webhook (so Astervis can read your CRM), run an initial sync to backfill existing data, then add an outbound webhook (so Bitrix24 pushes changes to Astervis in realtime). The whole thing takes a few minutes.
Create an inbound webhook in Bitrix24
In Bitrix24, open Developer resources → Other → Inbound webhook (older accounts: Applications → Webhooks → Add inbound webhook). Grant it CRM and User scopes — Astervis needs CRM to read leads, deals, contacts, companies and pipelines, and User to read departments and employees.
Bitrix24 generates a URL of the form:
https://your-portal.bitrix24.com/rest/1/abcdef0123456789/Copy it. The token is the long random segment in that path — treat it like a password.
Connect it in Astervis
In the Astervis admin, go to Settings → Integrations → Bitrix24. Paste the webhook URL and the application token, then click Verify. Astervis makes a test call to confirm the URL is reachable and the scopes are sufficient. When it passes, Save.
If verification fails, it's almost always the webhook scopes. Re-open the inbound webhook in Bitrix24 and make sure both CRM and User are ticked, then verify again.
Run the initial sync
With the connection saved, backfill your existing data. On the Bitrix24 integration page, trigger the syncs in this order so references resolve cleanly:
- Departments, then Employees — establishes the org chart first.
- Categories, then Pipeline stages — your pipeline definitions.
- Contacts and Companies.
- Leads and Deals — pick a date range for these. Start with the last few months, confirm it looks right, then widen the range for older history.
Each sync runs as a background job, so you can kick one off and watch its progress rather than holding the page open. Deal-stage history comes along with deals.
Initial sync time scales with how many records you have and the date range you pick. Large back-catalogues are best pulled in a couple of passes — recent data first, then older ranges — which also lets the sales dashboards become useful immediately.
Add the outbound webhook for realtime updates
The initial sync is a one-time backfill. To keep Astervis current without re-running syncs, have Bitrix24 push changes as they happen.
Astervis shows an outbound webhook URL on the same integration page — copy it. In Bitrix24, open Developer resources → Other → Outbound webhook, paste the Astervis URL as the handler, and subscribe to the CRM events you care about (deal added/updated, lead added/updated, contact and company changes). From now on, a deal moving stage or a contact being edited reaches Astervis within seconds.
Once the outbound webhook is live you shouldn't need the manual syncs again for day-to-day operation. Keep them for the occasional backfill — for example, importing an older date range you skipped the first time, or re-pulling after a large bulk edit in Bitrix24.
Using the synced data
The most visible payoff is on the sales dashboards. Because deals, their pipeline stages and their stage history are all synced, Astervis builds your sales views directly from real CRM data rather than a parallel spreadsheet:
- Deal counts and stage distribution across each category (pipeline funnel).
- Average sale price and sale-items breakdowns.
- Top incoming numbers and which deals they map to.
Per Astervis policy, analytics widgets show numeric values only — no currency symbols or codes. A deal's value still syncs from Bitrix24; it's just rendered as a plain number.
Beyond dashboards, the synced records power call-to-CRM linking. When a call lands, Astervis matches the other party's phone number against your synced contacts, leads and deals and attaches the call to the matching record — so an operator (or a supervisor reviewing later) sees who called and which deal it belongs to. Synced employees are how a call's extension resolves to a named operator in operator-performance and leaderboard reports.
Sync status and troubleshooting
Every sync runs as a background job with a visible lifecycle. On Settings → Integrations →
Bitrix24 you'll find the sync history with each job's status — pending, running,
completed, or failed. A failed job shows the error and can be retried; a successful one
records how many entities it pulled.
Next steps
Last updated on