How to Integrate ConnectiveOne with Odoo CRM

Important: Odoo CRM integration (module, iframe, webhooks) is implemented by the client's IT team. ConnectiveOne provides public guides and standard mechanisms (autologin, event_webhook_url); it is not part of the CO implementation estimate.

This guide describes typical ways to integrate ConnectiveOne with Odoo CRM: embedding the operator panel, webhook events, and contact/lead synchronization. It is intended for teams building an Odoo module on the client side.

What Can Be Integrated

Recommended Architecture

Principle: dialogues and routing stay in ConnectiveOne; Odoo holds CRM cards, activities, and manager directories.

Step 1. Embed Operator Panel

Full guide: How to integrate operator panel as widget in Odoo CRM.

Summary:

1. Match manager email in Odoo and ConnectiveOne.
2. Store login_key for autologin in Odoo secure storage.
3. Add iframe tab on res.partner / crm.lead.
4. Build URL server-side with client phone.

Step 2. Operator Panel Webhook in Odoo

ConnectiveOne Configuration

In operator_panel__connect_to_operator_with_msg:

{
  "auto_connect_operator": true,
  "subject_alias": "support",
  "event_webhook_url": "https://your-odoo.example.com/connectiveone/events"
}

Event list and payload format — webhook configuration.

Example Odoo Controller (Python)

from odoo import http
from odoo.http import request

class ConnectiveOneWebhook(http.Controller):

    @http.route("/connectiveone/events", type="json", auth="public", methods=["POST"], csrf=False)
    def receive_event(self, **kwargs):
        data = request.jsonrequest
        event_name = data.get("event_name")
        client = data.get("client") or {}
        phone = client.get("phone")
        partner = False
        if phone:
            partner = request.env["res.partner"].sudo().search([
                "|", ("phone", "ilike", phone[-9:]),
                ("mobile", "ilike", phone[-9:]),
            ], limit=1)

        if event_name == "chat_created" and partner:
            partner.activity_schedule(
                "mail.mail_activity_data_todo",
                summary="New ConnectiveOne chat",
                note=data.get("text", ""),
            )
        elif event_name == "chat_closed_by_operator" and partner:
            partner.message_post(body="ConnectiveOne chat closed by operator")

        return {"status": "ok"}

Add authentication for production (shared secret header, VPN, or mTLS).

Typical CRM Event Actions

Step 3. Leads and Contacts from Bot

Create Lead via Odoo External API

From Action Jail or scenario call Odoo External API:

// Example in custom action (pseudocode)
// authenticate → execute_kw('crm.lead', 'create', [{ name, phone, description }])

Recommended lead fields:

Step 4. Custom Fields and Identifiers

This enables correct dialogue deep links from iframe and webhook updates on the same card.

Step 5. Odoo System Parameters

Why Embed, Not Discuss

Duplicating chat in Odoo Discuss requires full message, attachment, and routing sync. That is costly to maintain and conflicts with ConnectiveOne skill groups.

Recommendation: operator panel iframe + webhooks for status and activities.

Implementation Checklist

• Odoo users = ConnectiveOne operators (email)
• Autologin URL tested on staging
• iframe renders in partner / lead form view
• Webhook endpoint handles chat_created and creates activity
• (Optional) Action Jail creates crm.lead on bot request
• CSP / cookies verified in production browsers
• Secrets not in Odoo module repository

Limitations

• Odoo Online may restrict custom controllers — check hosting plan
• Autologin requires valid login_key
• Webhook URL must be reachable from ConnectiveOne servers
• Full two-way message sync is a separate large scope

Related Articles

• Operator panel widget in Odoo
• Integrate operator panel as widget (general)
• Configure operator panel webhook
• Integrate via Custom Channel
• What are integrations