⚡Quick answer -
Paste three MyOperator webhook URLs into Bitrix24 (Inbound, Outbound) and MyOperator (After-Call), grant CRM + Telephony scopes to both webhooks, then place a test call—Bitrix24 will auto-create/-update the lead and attach the recording within 30 seconds.
Use it when you need a copy-paste-ready recipe to
(a) pop lead/contact details to agents on inbound calls,
(b) click-to-call from Bitrix24, and
(c) store every call’s activity, disposition, and recording link inside the CRM—without writing code.
Requirement | Minimum Value | Where to find it |
MyOperator Company ID | Any paid tier | MyOperator > Settings |
MyOperator plans | SUV and Above (New Plans) | _____ |
API Token & Secret | Active | MyOperator > Developer |
IVR ID | Peer-to-Peer enabled | MyOperator > IVR |
Bitrix24 Inbound Webhook | New URL | Bitrix24 > Apps > Dev. Resources |
Decide on unknown numbers | Yes / No | Business decision |
Alt text: video demo
Alt-text: Sequence diagram of call flow between Customer, MyOperator, and Bitrix24.
Alt text: Bitrix24 Integration page
Expected result: MyOperator is ready to push live call data and receive outbound triggers.
https://connect.myoperator.com/api/1.1/wf/obd_bitrix24• Open Users tab in the MyOperator ↔ Bitrix24 panel.
• Click Sync Users whenever you add new agents or change extensions.
Test | Action | Expected result |
Inbound | Call your MyOperator number from the test phone. | Lead/contact pops or is created; activity appears; recording URL arrives within 30s. |
Outbound | Click any phone field in Bitrix24 ➜ Call. | Desk/soft phone rings; call placed; activity + recording attached to CRM record. |
Logs | MyOperator ➜ Webhook Delivery ➜ 200 OK. | All three endpoints return 2xx. |
Symptom | Likely Cause | Fix |
No data in Bitrix24 | Wrong HTTP verb or Content-Type | Ensure POST + JSON in MyOperator. |
Outbound click-to-call silent | Event mismatch | The event must be an External phone call start. |
Recording link missing | Call < 5s or After-Call URL not set | Re-test with a longer call; confirm |
4xx/5xx in logs | Firewall blocks | Allowlist |
When does this NOT work?
• If your Bitrix24 plan blocks webhooks (free tier).
• If company policy forbids external call recordings—use Bitrix24 native telephony instead.
• In-Call API may arrive before a recording is available; the After-Call API patches the record.
• Payload limit: 512 KB—oversize metadata is truncated.
• Only voice calls are supported; SMS logs are ignored.
• Store API tokens in a secret manager (Vault, AWS SM, etc.).
• Do not paste raw webhook URLs in chat; they contain secrets.
• Follow your org’s retention policy for recordings (GDPR, HIPAA).
Collect before raising a ticket:
Who to contact:
• MyOperator Support: support@myoperator.com
• Bitrix24 Support: Bitrix24 portal ➜ Help ➜ Support.
Keywords: MyOperator Bitrix24 integration, call logging, webhook, click-to-call, CRM telephony