Skip to content

[META] Chatwoot integration — tracking umbrella #2014

@DAVIAMERICO242

Description

@DAVIAMERICO242

Meta-issue consolidating all open Chatwoot-integration reports.
Please do not open new Chatwoot issues — comment here instead.

Known symptoms

Connection / setup

  • 401 Unauthorized when connecting Evolution to Chatwoot
  • Cannot use internal Docker hostname for Chatwoot URL (Validation Error 400)
  • Cloudflare routing loops
  • QR Code generation stuck when Chatwoot integration is auto-enabled

Message delivery (Evolution → Chatwoot)

  • Group messages sent via API don't appear in Chatwoot
  • Messages show as empty / blank in Chatwoot
  • New messages don't appear as "Open" conversations
  • Outgoing messages show "Waiting for message. This may take a while." after Chatwoot 4.7.0 upgrade
  • Quoted / reply context lost after recent updates
  • Audio sending fails (unsupported MIME audio/opus) on Official WhatsApp API
  • Voice notes don't work
  • Self-sent messages from linked WhatsApp app appear as outgoing instead of private notes
  • contactsArrayMessage silently discarded (multi-number contact cards fail)
  • templateMessage fails to parse ("no body message found")
  • Backslash added before newlines / trailing newlines in messages
  • Images don't arrive from Chatwoot

Import / historical data

  • Contact import only works if Chatwoot is connected before first QR scan
  • CHATWOOT_IMPORT_DATABASE_CONNECTION_URI must use chatwoot_production DB (not chatwoot)
  • Historical import fails for @lid conversations despite syncFullHistory=true
  • Timezone incorrect (UTC-3) on created_at during import

Contact / ID handling

  • @lid in Chatwoot breaks identification (cross-linked with @lid umbrella)
  • Argentinian numbers (+549) map incorrectly, creating corrupt contacts
  • chatwootConversationId is undefined from Meta Ads / catalog (v2.3.4)

Infrastructure / reliability

  • "Timed out reading data from server" when sending messages (v2.3.7)
  • Excessive retry behavior causing API overload (polling / Redis backlog)
  • CHATWOOT_MESSAGE_READ=false has no effect
  • receiveWebhook causes timeout
  • Reconnecting an instance (without deleting it) stops forwarding messages — requires server restart

Feature requests

Known workaround (for historical import)

  • Connect Chatwoot BEFORE generating the QR Code on a fresh instance
  • Use CHATWOOT_IMPORT_DATABASE_CONNECTION_URI pointing to chatwoot_production
  • If messages stop after reconnect: restart the Evolution container or delete & recreate the instance

For maintainers

All duplicate Chatwoot issues are being closed with state_reason: duplicate pointing here. Use this thread as the single source of truth for the integration's health.


Reorganized as a meta-issue as part of the 2026-04 issue triage. Original reporter (@DAVIAMERICO242) and all community contributors remain credited in the comment history.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions