What is the quickest way to integrate MyOperator with Bitrix24 for inbound & outbound calls plus automatic logging?

What is the quickest way to integrate MyOperator with Bitrix24 for inbound & outbound calls plus automatic logging?

⚡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.

When should I use this guide?

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.


1. Prerequisites

Requirement

Minimum Value

Where to find it

MyOperator Company ID

Any paid tier

MyOperator > Settings

MyOperator plans

SUV and Above (New Plans)
Growth or higher (Old 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


Watch the video walkthrough

Alt text: video demo


2. Architecture at a glance

image.png

Alt-text: Sequence diagram of call flow between Customer, MyOperator, and Bitrix24.


4. Step-by-step configuration

4.1 Configure in MyOperator

  1. Sign in ➜ Settings ➜ Webhook Integrations ➜ Add.

image.png

Alt text: Bitrix24 Integration page

  1. Method = POST, Content-Type = JSON.
  2. Paste the three URLs from “Quick setup”.
  3. Temporarily leave the Bitrix24 Inbound Webhook URL blank—you will paste it in step 4.2-6.
  4. Click Save & Submit.

Expected result: MyOperator is ready to push live call data and receive outbound triggers.

4.2 Configure Bitrix24 (Inbound)

  1. Bitrix24 ➜ Menu ➜ Applications ➜ Developer Resources ➜ Inbound Webhook ➜ Add.
  2. Copy the generated URL.
  3. Scopes (minimum): CRM, User, Telephony, Telephony (outbound).
  4. Save.
  5. Return to MyOperator ➜ paste this URL into the “Inbound Webhook” field.
  6. Save again. 

4.3 Configure Bitrix24 (Outbound)

  1. Bitrix24 ➜ Applications ➜ Developer Resources ➜ Outbound Webhook ➜ Add.
  2. Handler URL: https://connect.myoperator.com/api/1.1/wf/obd_bitrix24
  3. Event: External phone call starts.
  4. Save.

5. Optional: Sync users

• Open Users tab in the MyOperator ↔ Bitrix24 panel.

• Click Sync Users whenever you add new agents or change extensions.


6. Validate end-to-end

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.


7. Troubleshooting & flip-side cases

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 dispose_call_api URL.

4xx/5xx in logs

Firewall blocks

Allowlist connect.myoperator.com on port 443.

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.


8. Edge cases & limitations

• 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.


9. Security & privacy

• 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).


10. Rollback/disable

  1. MyOperator ➜ Webhook Integrations ➜ Disable or Delete endpoints.
  2. Bitrix24 ➜ Delete both Inbound & Outbound webhooks.
  3. Document the change in your internal runbook. 

11. Escalation & support

Collect before raising a ticket:

  • MyOperator Webhook Delivery logs (screenshots).
  • Masked handler URLs.• Company ID, IVR ID, sample Call ID.

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