🎯 Goal: Connect MyOperator telephony with Bitrix24 CRM so you can: (1) auto‑create/update leads on inbound calls, (2) place outbound calls from Bitrix24, and (3) auto‑log call activities with recording links.

📚 Table of contents

• When & why to use this
• Prerequisites
• Architecture at a glance
• Quick setup (copy‑paste)
• Step‑by‑step: Configure in MyOperator
• Step‑by‑step: Configure in Bitrix24 (Inbound)
• Step‑by‑step: Configure in Bitrix24 (Outbound)
• Optional: Sync users
• Validate end‑to‑end
• Troubleshooting
• Edge cases & limitations
• Security & privacy
• Rollback / disable
• Escalation & support
• Related articles
• Structured data (HowTo + FAQPage)
• Change log

🧭 When & why to use this

• 📥 Inbound: Create/update leads when customers call; pop lead/contact info to agents.
• 📤 Outbound: Click‑to‑call from Bitrix24; push results & recordings back to CRM.
• 📝 Auto logging: Eliminate manual entry; keep activities and recordings attached to CRM entities.

📋 Prerequisites

• ✅ MyOperator Company ID
• ✅ API Token & Secret Token (MyOperator)
• ✅ IVR ID with Peer‑to‑Peer enabled (for call routing)
• ✅ Bitrix24 Inbound Webhook URL (you’ll generate this below)
• 🔎 Decide: Create leads for unknown numbers? (Yes/No)

💡 Tip: Have one test customer number and one agent extension ready.

🧩 Architecture at a glance

⚡ Quick setup (copy‑paste)

All endpoints use HTTPS. Use the exact keys shown below.

In‑Call API (MyOperator → Bitrix24 during call)

https://connect.myoperator.com/api/1.1/wf/bitrix24_incall_we…  ← Copy exact URL from your MyOperator UI (In‑Call API)

After‑Call API (MyOperator → Bitrix24 after call)

https://connect.myoperator.com/api/1.1/wf/dispose_call_api/

Outbound Handler (Bitrix24 → MyOperator)

https://connect.myoperator.com/api/1.1/wf/obd_bitrix24

MyOperator Webhook settings

• Request Method: POST
• Content‑Type: application/json

✅ These values match the official integration flow. If your In‑Call URL shows an ellipsis in this doc, copy it directly from your MyOperator dashboard to avoid truncation.

🪜 Step‑by‑step: Configure in MyOperator

1. Sign in to the MyOperator dashboard.
2. Go to Settings → Webhook Integrations and click Add.
3. Set Request Method = POST and Content Type = JSON.
4. Paste the three endpoints from Quick setup into their respective fields:
• In‑Call API → (paste full URL from your MyOperator UI)
• After‑Call API → https://connect.myoperator.com/api/1.1/wf/dispose_call_api/
• Outbound Handler → https://connect.myoperator.com/api/1.1/wf/obd_bitrix24
5. Paste your Bitrix24 Inbound Webhook URL (you’ll generate it in the next section; you can return and add it later).
6. Save & Submit to store integration settings.

🎯 Expected result: MyOperator is ready to send in‑call updates and after‑call dispositions to Bitrix24, and to receive outbound triggers from Bitrix24.

🏷️ Step‑by‑step: Configure in Bitrix24 (Inbound)

1. Log in to Bitrix24 (admin).
2. Navigate: Menu → Applications → Developer Resources → Inbound Webhook → Add.
3. Copy the generated Inbound Webhook URL and keep it handy.
4. Permissions (minimum):
• CRM
• User
• Telephony
• Telephony (outbound calls)
5. Save & Close.
6. Go back to MyOperator and paste this Inbound Webhook URL where requested.

📞 Step‑by‑step: Configure in Bitrix24 (Outbound)

1. Navigate: Menu → Applications → Developer Resources → Outbound Webhook → Add.
2. Handler URL → paste:

https://connect.myoperator.com/api/1.1/wf/obd_bitrix24

3. Event → External phone call start.
4. Save & Close.

👥 Optional: Sync users

• Open the Users tab in the MyOperator ↔ Bitrix24 panel.
• Click Sync Users when:
• you’ve added new users after integration, or
• you need to refresh user mapping.
• 🔔 Button appears only when a valid Company ID is entered and data exists.

🧪 Validate end‑to‑end

A) Inbound test

• Place a test inbound call to your MyOperator number.
• Expected in Bitrix24: lead/contact pops or is created/updated; an activity appears with recording URL once available.

B) Outbound test

• From Bitrix24, initiate an outbound call (click‑to‑call).
• Expected in MyOperator: call is placed via the configured line; results flow back to Bitrix24 as an activity + recording.

C) Check logs

• In MyOperator, open Webhook Delivery/Logs and confirm HTTP 200 OK for the events.

D) Manual pings (optional)

# Outbound handler smoke test (should return a JSON or 200)curl -I "https://connect.myoperator.com/api/1.1/wf/obd_bitrix24"# After-call endpoint reachabilitycurl -I "https://connect.myoperator.com/api/1.1/wf/dispose_call_api/"

🛠️ Troubleshooting

No data appears in Bitrix24

• ✅ Confirm POST + JSON in MyOperator settings.
• 🔗 Ensure you pasted the full In‑Call API URL (not truncated) and the Bitrix24 Inbound Webhook URL.
• 🔐 Check that API Token/Secret and Company ID are valid in MyOperator (if required by your plan).
• 📜 Bitrix24 permissions include CRM and Telephony.

Outbound click‑to‑call does nothing

• 🧭 Verify Outbound Webhook → Handler URL is set to …/obd_bitrix24 and Event = External phone call start`.
• 🔁 Re‑authenticate your Bitrix24 admin session; retry.

Recording link missing

• ⏱️ Very short calls may not generate recordings.
• 🎯 Confirm After‑Call API (…/dispose_call_api/) is configured.

User not found / mapping issues

• 🔄 Run Sync Users in the MyOperator panel.

4xx/5xx in MyOperator Logs

• ⌛ Check for timeouts/firewalls between Bitrix24 ↔ MyOperator.
• 🧪 Retry with a simpler test call; examine payload size.

⚖️ Edge cases & limitations

• 📞 Inbound vs. After‑Call: In‑Call updates may arrive before recordings are ready; After‑Call pushes final disposition + recording.
• 🌐 Network policies: firewalls/proxies may block external webhook calls—allowlist the connect.myoperator.com domain.
• 📏 Payload size: extremely large metadata or attachments may be truncated by intermediaries.
• 👤 Unknown numbers: decide whether to create leads for new numbers (recommended for marketing lines).

🔒 Security & privacy

• 🔑 Store API tokens and webhook URLs in a secret manager.
• 🙈 Don’t share raw URLs or recordings in public chats.
• 🗄️ Follow your org’s data‑retention policy for PII and call recordings.

🧹 Rollback / disable

• In MyOperator → Webhook Integrations, disable or remove the Bitrix24 endpoints.
• In Bitrix24, delete the Inbound and Outbound webhooks.
• Document the rollback in your change log.

🆘 Escalation & support

Collect before raising a ticket

• 🧾 MyOperator Webhook Delivery/Logs screenshots with timestamps.
• 🔗 Exact handler URLs you configured (mask tokens).
• 🆔 Company ID, IVR ID, and a sample Call ID or timestamps.

Who to contact

• 📮 MyOperator Support: support@myoperator.co
• 🧭 Bitrix24 Support: via your Bitrix24 portal → Help → Support.

What to say

“We set In‑Call, After‑Call, and Outbound endpoints between MyOperator and Bitrix24. We observe . Here are logs, timestamps, handler URLs, and test numbers.”

🔗 Related articles

• Verify webhook delivery & logs in MyOperator → /kb/myoperator/manage-webhooks
• Bitrix24: Permissions & webhook scopes → /kb/bitrix24/webhook-permissions
• Troubleshoot call recordings in Bitrix24 → /kb/bitrix24/recordings-troubleshooting

🧱 Structured data (HowTo + FAQPage)

HowTo

<script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "HowTo",  "name": "Integrate MyOperator with Bitrix24 (inbound, outbound, auto-logging)",  "totalTime": "PT25M",  "step": [    {"@type": "HowToStep", "name": "Configure in MyOperator", "text": "Set POST + JSON. Paste In-Call, After-Call, and Outbound Handler URLs.", "url": "#mo-steps"},    {"@type": "HowToStep", "name": "Create Bitrix24 Inbound Webhook", "text": "Generate URL and grant CRM + Telephony permissions.", "url": "#b24-inbound"},    {"@type": "HowToStep", "name": "Create Bitrix24 Outbound Webhook", "text": "Set Handler URL to /obd_bitrix24 and event External phone call start.", "url": "#b24-outbound"},    {"@type": "HowToStep", "name": "Validate", "text": "Place inbound & outbound test calls; confirm 200 OK in MyOperator logs.", "url": "#validate"}  ],  "tool": [    {"@type": "HowToTool", "name": "MyOperator Dashboard"},    {"@type": "HowToTool", "name": "Bitrix24 Portal"}  ],  "image": {"@type": "ImageObject", "url": "./images/myoperator-webhook-settings.png", "caption": "MyOperator Webhook settings (POST + JSON)."}}</script>

FAQPage

<script type="application/ld+json">{  "@context": "https://schema.org",  "@type": "FAQPage",  "mainEntity": [    {"@type": "Question", "name": "Do I need POST or GET?", "acceptedAnswer": {"@type": "Answer", "text": "Use POST with application/json for MyOperator ↔ Bitrix24 integration."}},    {"@type": "Question", "name": "What permissions must the Bitrix24 webhook have?", "acceptedAnswer": {"@type": "Answer", "text": "CRM, User, Telephony, and Telephony (outbound calls)."}},    {"@type": "Question", "name": "How do I get recordings to appear in Bitrix24?", "acceptedAnswer": {"@type": "Answer", "text": "Ensure the After-Call API is configured and the call duration meets recording thresholds."}}  ]}</script>