Hello Alex,

At the moment, Odoo does not provide an official documented identify() API for externally embedded Live Chat widgets similar to Intercom or Crisp.

By default, the external widget mainly works with anonymous mail.guest sessions, and parameters like partner_id or username are not automatically mapped to the Discuss operator view.

That said, your findings are correct methods like _process_extra_channel_params() and getSessionExtraParams() are typical extension points used for custom implementations. In self-hosted deployments, the usual approach is to extend the widget/backend flow to pass authenticated SaaS user data and link it to a res.partner or customized guest session.

So in short:

• No official out-of-the-box identity sync for external SaaS embeds
• Achievable through customization/extensions
• Common approach is custom session mapping between your SaaS auth layer and Odoo Live Chat

Hope this works for you! If you need any help implementing this or want a more optimized approach, feel free to reach out for further discussion.

Regards,

Zehntech Technologies Inc.

santosh.sekwadia@zehntech.com

There's no official identify() API in Odoo Live Chat for external embedding. It simply wasn't designed for that use case. The most reliable workaround is calling Odoo via JSON-RPC from your backend to resolve the mail.guest record tied to your res.partner.id, then setting the dgid cookie before the widget loads. Alternatively, if you're open to a small custom module, _process_extra_channel_params is a real  override point you can use to inject partner identity server-side when the channel is created.